cryptexlock.me - robtex.com
cryptexlock.me
| DNSSEC | ⚠️ Not signed | ||||||
| A | 116.202.23.223🇩🇪 Hetzner116.202.0.0/16 HETZNER-DC | ||||||
| PTR | static.223.23.202.116.clients.your-server.de | ||||||
| NS | ns21.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2141::b🇺🇸 GODADDY-DNS2603:5:2140::/44 | ||||||
| PTR | ns21.domaincontrol.com | ||||||
| A | 97.74.100.11🇺🇸 GODADDY-DNS97.74.100.0/23 | ||||||
| PTR | ns21.domaincontrol.com | ||||||
| NS | ns22.domaincontrol.com | ||||||
| A | 2603:5:2241::b🇺🇸 GODADDY-DNS2603:5:2240::/44 | ||||||
| PTR | ns22.domaincontrol.com | ||||||
| A | 173.201.68.11🇺🇸 GODADDY-DNS173.201.68.0/23 | ||||||
| PTR | ns22.domaincontrol.com | ||||||
| MX | mx.yandex.net ⭐ | ||||||
| A | 2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| A | 77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| TXT | google-site-verification=onisqH2Sn42PgaXrMZtyztv2ZW2vSImkKUJGAJIDZBk | ||||||
| TXT | yandex-verification: 596a6e4692609d26 | ||||||
| TXT | google-site-verification=1AXIEOSsny5nhJWcX_iGoRSPk6KfjDGbFCAkCL5SeTM | ||||||
| SOA | ns21.domaincontrol.comdns@jomax.net 2022-03-21 #2 | ||||||
me
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.nic.me ⭐ | ||||||
| NS | a2.nic.me | ||||||
| NS | b0.nic.me | ||||||
| NS | b2.nic.me | ||||||
| NS | c0.nic.me | ||||||
| SOA | a0.nic.mehostmaster@donuts.email serial=1774480919 | ||||||
Same first word
cryptexlock.me |
DNS History
4 records (4 active, 0 former)
●NSns21.domaincontrol.com2026-03-06 → 2026-03-25 · 2 obs
● 2026-03-25 23:50:10
●NSns22.domaincontrol.com2026-03-06 → 2026-03-25 · 2 obs
● 2026-03-25 23:50:10
●MXmx.yandex.net2026-03-06 → 2026-03-25 · 2 obs
● 2026-03-25 23:50:10
●A116.202.23.2232026-03-06 → 2026-03-25 · 2 obs
● 2026-03-25 23:50:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| me | a0.nic.me, a2.nic.me, b0.nic.me, b2.nic.me... | 10 records |
| cryptexlock.me | ns21.domaincontrol.com, ns22.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.68.11
NS records: ns21.domaincontrol.com, ns22.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cryptexlock.me (unsigned zone)
⏱️ Timing
Total: 384ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 116.202.23.223 |
| NS | 2 | ns21.domaincontrol.com, ns22.domaincontrol.com |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 3 | google-site-verification=onisqH2Sn42PgaX, yandex-verification: 596a6e4692609d26... |
| SOA | 1 | ns21.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 10
In-bailiwick: 10 (a0.nic.me, a2.nic.me, b0.nic.me...)
Analysis
IP Addresses
cryptexlock.me points to a single IP address: 116.202.23.223.
Other host names such as hashex.org and static.223.23.202.116.clients.your-server.de share IP numbers with cryptexlock.me.
Name Servers
cryptexlock.me is delegated to two name servers: ns21.domaincontrol.com and ns22.domaincontrol.com.
cryptexlock.me uses the same name server setup as other domains, including rrengineers.com, dcarola.com, tabletdrawing.com, dropbacktracks.com and ratiojobs.io.
Host names with two IP numbers:
ns21.domaincontrol.com points to 2603:5:2141::b and 97.74.100.11.
ns22.domaincontrol.com points to 2603:5:2241::b and 173.201.68.11.
Mail Servers
The mail server for cryptexlock.me is mx.yandex.net.
cryptexlock.me uses the same mail server setup as other domains, for instance www.nadev.ru, restream.ru, akadem66.ru, naupers.ru and ellamartino.ru.
cryptexlock.me shares some mail servers with other domains at least partially, for example citycard.me, mybuketi.ru and piston.by.
Hostname mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.