View on GitHub

DNSViz: A DNS visualization tool

att.net

Updated: 2026-01-03 01:19:53 UTC (40 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • att.net/A
  • att.net/MX
  • att.net/NS
  • att.net/SOA
  • att.net/TXT
Secure (1)
  • net/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 21831)
  • ./DNSKEY (alg 8, id 38696)
  • ./DNSKEY (alg 8, id 61809)
  • NSEC3 proving non-existence of att.net/DS
  • net/DNSKEY (alg 13, id 17133)
  • net/DNSKEY (alg 13, id 37331)
  • net/DS (alg 13, id 37331)

Delegation statusDelegation status

Insecure (1)
  • net to att.net
Secure (1)
  • . to net

NoticesNotices

Errors (5)
  • att.net zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (68.94.156.128, 68.94.156.130, 99.99.99.128, 99.99.99.130, 2001:1890:1ff:9f0:68:94:156:128, 2001:1890:1ff:9f0:68:94:156:130, 2001:1890:1ff:9f1:99:99:99:130)
  • att.net/MX: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (2001:1890:1ff:9f1:99:99:99:130, TCP_-_EDNS0_4096_D)
  • att.net/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:1890:1ff:9f0:68:94:156:130, UDP_-_EDNS0_512_D_KN)
  • att.net/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (68.94.156.128, 68.94.156.130, 99.99.99.128, 99.99.99.130, 2001:1890:1ff:9f0:68:94:156:130, 2001:1890:1ff:9f1:99:99:99:130, TCP_-_EDNS0_4096_D_N)
  • att.net/SOA: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (2001:1890:1ff:9f0:68:94:156:128, TCP_-_EDNS0_4096_D_N)
Warnings (5)
  • att.net/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:1890:1ff:9f1:99:99:99:130, UDP_-_EDNS0_4096_D_KN)
  • net to att.net: Authoritative AAAA records exist for macu.ma.mt.np.els-gms.att.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • net to att.net: Authoritative AAAA records exist for ohcu.oh.mt.np.els-gms.att.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • net to att.net: Authoritative AAAA records exist for orcu.or.br.np.els-gms.att.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • net to att.net: Authoritative AAAA records exist for wycu.wy.br.np.els-gms.att.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph