code.tatar - dns.ninja
code.tatar
tatar
| DNSSEC | ⚠️ Not signed | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | c.tld-servers.ru | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=650358544 | ||||||
Same first word
Similar names
DNS History
4 records (4 active, 0 former)
●MXmx.yandex.net2026-10-03 → 2026-10-10 · 2 obs
● 2026-10-10 17:34:34
●A217.18.62.1322026-10-03 → 2026-10-10 · 2 obs
● 2026-10-10 17:34:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| tatar | d.dns.ripn.net, a.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net... | 12 records |
| code.tatar | ns1.reg.ru, ns2.reg.ru | - |
✅ Authoritative Response
Server:176.99.13.12
NS records: ns1.reg.ru, ns2.reg.ru
🔒 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: 3266ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 217.18.62.132 |
| NS | 2 | ns1.reg.ru, ns2.reg.ru |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 1 | yandex-verification: db8e3c50128aa6b3 |
| SOA | 1 | ns1.reg.ru hostmaster.ns1.reg.ru |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (d.dns.ripn.net, d.dns.ripn.net, a.dns.ripn.net...)
Analysis
IP Addresses
code.tatar resolves to one IP address: 217.18.62.132.
Name Servers
code.tatar has two authoritative name servers — ns1.reg.ru and ns2.reg.ru.
Hostnames that resolve to 10 IP addresses:
ns1.reg.ru points to 176.99.13.11, 176.99.13.13, 176.99.13.15 and 7 other IP addresses.
ns2.reg.ru points to 176.99.13.12, 176.99.13.14, 176.99.13.16 and 7 other IP addresses.
Mail Servers
Mail for code.tatar is handled by a single mail server, mx.yandex.net.
mx.yandex.net resolves to two IP numbers — 77.88.21.249 and 2a02:6b8::311.