getc.dev - robtex.com
getc.dev
| DNSSEC | ⚠️ Not signed | ||||||
| A | 62.109.30.229🇷🇺 AS2918262.109.28.0/22 | ||||||
| PTR | archon.fvds.ru | ||||||
| NS | dns1.yandex.net ⭐ | ||||||
| A | 2a02:6b8::213TELETECH2a02:6b8::/32 Yandex network | ||||||
| A | 213.180.204.213 | ||||||
| NS | dns2.yandex.net | ||||||
| A | 2a02:6b8:0:1::213TELETECH2a02:6b8::/32 Yandex network | ||||||
| A | 93.158.134.213 | ||||||
| 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 | v=spf1 redirect=_spf.yandex.net | ||||||
| SOA | dns1.yandex.netdns-hosting@yandex.ru serial=23 | ||||||
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
4 records (4 active, 0 former)
●NSdns1.yandex.net2026-09-11 → 2026-09-20 · 2 obs
● 2026-09-20 07:31:10
●NSdns2.yandex.net2026-09-11 → 2026-09-20 · 2 obs
● 2026-09-20 07:31:10
●MXmx.yandex.net2026-09-11 → 2026-09-20 · 2 obs
● 2026-09-20 07:31:10
●A62.109.30.2292026-09-11 → 2026-09-20 · 2 obs
● 2026-09-20 07:31:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | 10 records |
| getc.dev | dns2.yandex.net, dns1.yandex.net | - |
✅ Authoritative Response
Server:93.158.134.213
NS records: dns2.yandex.net, dns1.yandex.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)
⏱️ Timing
Total: 2293ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns2.yandex.net, dns1.yandex.net |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 1 | v=spf1 redirect=_spf.yandex.net |
| SOA | 1 | dns1.yandex.net dns-hosting.yandex.ru |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
getc.dev has exactly one IP address — 62.109.30.229.
archon.fvds.ru is an example of another host name that shares IP numbers with getc.dev.
Name Servers
getc.dev has two authoritative name servers — dns1.yandex.net and dns2.yandex.net.
The name server configuration of getc.dev is shared with other domains, for instance pogodin.ru, pskovkotel.ru, geely-pokrovka38.ru and two others.
getc.dev partially shares its NS delegation with several other domains, including pekitesnami.ru, vayner.ru, softwood.ru and two others.
These name servers are regularly seen alongside dns1.yandex.ru and dns2.yandex.ru as name servers.
Both dns1.yandex.net and dns2.yandex.net have two IP addresses each. dns1.yandex.net resolves to 213.180.204.213 and 2a02:6b8::213; dns2.yandex.net resolves to 93.158.134.213 and 2a02:6b8:0:1::213.
Mail Servers
getc.dev uses one mail server — mx.yandex.net.
The mail server setup of getc.dev matches that of other domains such as ets-eng.com, apply-marine.ru, design-marusya.ru and two others.
getc.dev partially shares its mail servers with other domains, xn-----7kcbajcvt8dlkddgjhel1dygih.xn--p1ai and klimatika.su being examples.
The host mx.yandex.net resolves to 77.88.21.249 and 2a02:6b8::311 — two IP addresses.