DNS lookup
Everything DNS says about a domain: traced from the root servers down, every record type asked of the domain's own nameservers, each nameserver checked, then every hostname and policy record it points at followed, with SPF, DMARC, DKIM and DNSSEC checked along the way.
204.14.183.1
1.183.14.204.in-addr.arpa
Zone 183.14.204.in-addr.arpa92 queries in 0.5 s2026-11-09 06:11:24 UTCNot DNSSEC-signed
- Note 183.14.204.in-addr.arpa isn't signed with DNSSEC, so resolvers can't tell forged answers from real ones.
Records
Asked directly of ns1-07.azure-dns.com (13.107.236.7), an authoritative server: no cache in between, so these are the live values.
PTR Reverse pointer
| 3600 | PTR | ns3-01.azure-dns.org. |
ANY query: refused politely (RFC 8482)
| 300 | HINFO | "RFC8482" "" |
No records of type A, AAAA, CNAME, DNAME, NS, SOA, MX, TXT, CAA, HTTPS, SVCB, SRV, NAPTR, DS, DNSKEY, CDS, CDNSKEY, NSEC3PARAM, TLSA, SSHFP, LOC, HINFO, RP, URI, SPF, OPENPGPKEY, ZONEMD, CSYNC.
Resolution trace
- .asked i.root-servers.net 192.36.148.175.9 ms
Referral to in-addr.arpa. signed (4 DS)
- c.in-addr-servers.arpa 196.216.169.10 2001:43f8:110::10
- b.in-addr-servers.arpa 199.253.183.183 2001:500:87::87
- e.in-addr-servers.arpa 203.119.86.101 2001:dd8:6::101
- f.in-addr-servers.arpa 193.0.9.1 2a13:27c0:30::1
- a.in-addr-servers.arpa 199.180.182.53 2620:37:e000::53
- d.in-addr-servers.arpa 200.10.60.53 2001:13c7:7010::53
- in-addr.arpa.asked b.in-addr-servers.arpa 199.253.183.1836.4 ms
Referral to 204.in-addr.arpa. signed (1 DS)
- r.arin.net 199.180.180.63 2001:500:f0::63
- u.arin.net 204.61.216.50 2001:500:14:6050:ad::1
- x.arin.net 199.180.180.63 2001:500:f0::63
- y.arin.net 192.82.134.30 2001:500:127::30
- z.arin.net 199.180.180.63 2001:500:f0::63
- arin.authdns.ripe.net 193.0.9.10 2a13:27c0:30::10
No glue for r.arin.net, u.arin.net, x.arin.net, y.arin.net, z.arin.net, arin.authdns.ripe.net: addresses looked up via a resolver.
199.180.182.53 failed: NOERROR
- 204.in-addr.arpa.asked arin.authdns.ripe.net 193.0.9.1011 ms
Referral to 183.14.204.in-addr.arpa. unsigned delegation
- ns3-07.azure-dns.org 204.14.183.7 2a01:111:4000:700::7
- ns4-07.azure-dns.info 208.84.5.7 2620:1ec:bda:700::7
- ns1-07.azure-dns.com 13.107.236.7 2603:1061:0:700::7
- ns2-07.azure-dns.net 150.171.21.7 2620:1ec:8ec:700::7
No glue for ns3-07.azure-dns.org, ns4-07.azure-dns.info, ns1-07.azure-dns.com, ns2-07.azure-dns.net: addresses looked up via a resolver.
199.180.180.63 failed: NOERROR
- 183.14.204.in-addr.arpa.asked ns2-07.azure-dns.net 150.171.21.76.0 ms
Answer (authoritative):
1.183.14.204.in-addr.arpa. 3600 PTR ns3-01.azure-dns.org.
Nameservers
Every address of every nameserver, asked for 183.14.204.in-addr.arpa's SOA. "Parent" means the 204.in-addr.arpa zone delegates to it; "zone" means 183.14.204.in-addr.arpa lists it itself.
| Nameserver | Listed in | Address | Status | Serial | Time |
|---|---|---|---|---|---|
| ns1-07.azure-dns.com | parent + zone | 13.107.236.7 glue | authoritative | 1 | 6.2 ms |
| 2603:1061:0:700::7 glue | authoritative | 1 | 6.2 ms | ||
| ns2-07.azure-dns.net | parent + zone | 150.171.21.7 glue | authoritative | 1 | 6.2 ms |
| 2620:1ec:8ec:700::7 glue | authoritative | 1 | 6.3 ms | ||
| ns3-07.azure-dns.org | parent + zone | 204.14.183.7 glue | authoritative | 1 | 6.4 ms |
| 2a01:111:4000:700::7 glue | authoritative | 1 | 6.4 ms | ||
| ns4-07.azure-dns.info | parent + zone | 208.84.5.7 glue | authoritative | 1 | 6.3 ms |
| 2620:1ec:bda:700::7 glue | authoritative | 1 | 6.4 ms |
DNSSEC
183.14.204.in-addr.arpa isn't signed: no DS at the parent and no DNSKEY in the zone.
Hosts and reverse DNS
Every hostname the records point at, resolved to its addresses; each address's PTR (reverse DNS), with ✓ where the PTR name resolves back to the same address.
| Host | Address | Reverse DNS (PTR) |
|---|---|---|
ns1-07.azure-dns.com nameserver | 13.107.236.7 | ns1-07.azure-dns.com ✓ |
| 2603:1061:0:700::7 | ns1-07.azure-dns.com ✓ | |
ns2-07.azure-dns.net nameserver | 150.171.21.7 | ns2-07.azure-dns.net ✓ |
| 2620:1ec:8ec:700::7 | ns2-07.azure-dns.net ✓ | |
ns3-07.azure-dns.org nameserver | 204.14.183.7 | ns3-07.azure-dns.org ✓ |
| 2a01:111:4000:700::7 | ns3-07.azure-dns.org ✓ | |
ns4-07.azure-dns.info nameserver | 208.84.5.7 | ns4-07.azure-dns.info ✓ |
| 2620:1ec:bda:700::7 | ns4-07.azure-dns.info ✓ | |
ns3-01.azure-dns.org PTR target | 204.14.183.1 | ns3-01.azure-dns.org ✓ |
| 2a01:111:4000:700::1 | ns3-01.azure-dns.org ✓ |
Public resolvers
What four public resolvers answer right now, from their caches. Highlighted values differ from the authoritative answer: either a recent change they haven't picked up yet (the TTL says how long until they do), or, for A and AAAA, a CDN or geo-routed site handing each resolver location its own addresses.
| Resolver | PTR |
|---|---|
| Cloudflare 1.1.1.1 | ns3-01.azure-dns.org. TTL 3600 |
| Google 8.8.8.8 | ns3-01.azure-dns.org. TTL 1258 |
| Quad9 9.9.9.9 | ns3-01.azure-dns.org. TTL 3600 |
| OpenDNS 208.67.222.222 | ns3-01.azure-dns.org. TTL 1387 |
Text dump
; DNS report for 1.183.14.204.in-addr.arpa (204.14.183.1) ; 2026-11-09 06:11:24 UTC, 92 queries in 0.50 s, zone 183.14.204.in-addr.arpa ;; FINDINGS ; [INFO] 183.14.204.in-addr.arpa isn't signed with DNSSEC, so resolvers can't tell forged answers from real ones. ;; RECORDS (authoritative, from ns1-07.azure-dns.com (13.107.236.7)) 1.183.14.204.in-addr.arpa. 3600 IN PTR ns3-01.azure-dns.org. ;; TRACE ; 1.183.14.204.in-addr.arpa PTR ; . @i.root-servers.net (192.36.148.17) 5.9 ms [NOERROR qr]: referral to in-addr.arpa. in-addr.arpa. NS c.in-addr-servers.arpa. ; 196.216.169.10 2001:43f8:110::10 in-addr.arpa. NS b.in-addr-servers.arpa. ; 199.253.183.183 2001:500:87::87 in-addr.arpa. NS e.in-addr-servers.arpa. ; 203.119.86.101 2001:dd8:6::101 in-addr.arpa. NS f.in-addr-servers.arpa. ; 193.0.9.1 2a13:27c0:30::1 in-addr.arpa. NS a.in-addr-servers.arpa. ; 199.180.182.53 2620:37:e000::53 in-addr.arpa. NS d.in-addr-servers.arpa. ; 200.10.60.53 2001:13c7:7010::53 in-addr.arpa. 86400 IN DS 63982 8 2 AAF4FB5D213EF25AE44679032EBE3514C487D7ABD99D7F5FEC3383D030733C73 in-addr.arpa. 86400 IN DS 54956 8 2 E0E2BF5CFBD66572CA05EC18267D91509BA6A9405AF05C3FD4141DFA45200C08 in-addr.arpa. 86400 IN DS 47054 8 2 5CAFCCEC201D1933B4C9F6A9C8F51E51F3B39979058AC21B8DF1B1F281CBC6F2 in-addr.arpa. 86400 IN DS 53696 8 2 13E5501C56B20394DA921B51412D48B7089C5EB6957A7C58553C4D4D424F04DF ; in-addr.arpa. @b.in-addr-servers.arpa (199.253.183.183) 6.4 ms [NOERROR qr]: referral to 204.in-addr.arpa. 204.in-addr.arpa. NS r.arin.net. ; 199.180.180.63 2001:500:f0::63 204.in-addr.arpa. NS u.arin.net. ; 204.61.216.50 2001:500:14:6050:ad::1 204.in-addr.arpa. NS x.arin.net. ; 199.180.180.63 2001:500:f0::63 204.in-addr.arpa. NS y.arin.net. ; 192.82.134.30 2001:500:127::30 204.in-addr.arpa. NS z.arin.net. ; 199.180.180.63 2001:500:f0::63 204.in-addr.arpa. NS arin.authdns.ripe.net. ; 193.0.9.10 2a13:27c0:30::10 204.in-addr.arpa. 86400 IN DS 16354 8 2 9D0810993F70DAE9B86EAECAB3CFBBB48BCAF0A35C5288548C95A9D9F8C7EDE2 ; 204.in-addr.arpa. @arin.authdns.ripe.net (193.0.9.10) 11 ms [NOERROR qr]: referral to 183.14.204.in-addr.arpa. 183.14.204.in-addr.arpa. NS ns3-07.azure-dns.org. ; 204.14.183.7 2a01:111:4000:700::7 183.14.204.in-addr.arpa. NS ns4-07.azure-dns.info. ; 208.84.5.7 2620:1ec:bda:700::7 183.14.204.in-addr.arpa. NS ns1-07.azure-dns.com. ; 13.107.236.7 2603:1061:0:700::7 183.14.204.in-addr.arpa. NS ns2-07.azure-dns.net. ; 150.171.21.7 2620:1ec:8ec:700::7 ; 183.14.204.in-addr.arpa. @ns2-07.azure-dns.net (150.171.21.7) 6.0 ms [NOERROR qr aa ad]: answer 1.183.14.204.in-addr.arpa. 3600 IN PTR ns3-01.azure-dns.org. ;; NAMESERVERS (SOA asked of each address) ; ns1-07.azure-dns.com [parent+zone] ; 13.107.236.7 ok 1 6.2 ms ; 2603:1061:0:700::7 ok 1 6.2 ms ; ns2-07.azure-dns.net [parent+zone] ; 150.171.21.7 ok 1 6.2 ms ; 2620:1ec:8ec:700::7 ok 1 6.3 ms ; ns3-07.azure-dns.org [parent+zone] ; 204.14.183.7 ok 1 6.4 ms ; 2a01:111:4000:700::7 ok 1 6.4 ms ; ns4-07.azure-dns.info [parent+zone] ; 208.84.5.7 ok 1 6.3 ms ; 2620:1ec:bda:700::7 ok 1 6.4 ms ;; DNSSEC: unsigned ;; HOSTS ; ns1-07.azure-dns.com (nameserver) ; 13.107.236.7 PTR ns1-07.azure-dns.com (confirmed) ; 2603:1061:0:700::7 PTR ns1-07.azure-dns.com (confirmed) ; ns2-07.azure-dns.net (nameserver) ; 150.171.21.7 PTR ns2-07.azure-dns.net (confirmed) ; 2620:1ec:8ec:700::7 PTR ns2-07.azure-dns.net (confirmed) ; ns3-07.azure-dns.org (nameserver) ; 204.14.183.7 PTR ns3-07.azure-dns.org (confirmed) ; 2a01:111:4000:700::7 PTR ns3-07.azure-dns.org (confirmed) ; ns4-07.azure-dns.info (nameserver) ; 208.84.5.7 PTR ns4-07.azure-dns.info (confirmed) ; 2620:1ec:bda:700::7 PTR ns4-07.azure-dns.info (confirmed) ; ns3-01.azure-dns.org (PTR target) ; 204.14.183.1 PTR ns3-01.azure-dns.org (confirmed) ; 2a01:111:4000:700::1 PTR ns3-01.azure-dns.org (confirmed) ;; PUBLIC RESOLVERS ; Cloudflare PTR ns3-01.azure-dns.org. ttl 3600 ; Google PTR ns3-01.azure-dns.org. ttl 1258 ; Quad9 PTR ns3-01.azure-dns.org. ttl 3600 ; OpenDNS PTR ns3-01.azure-dns.org. ttl 1387