View on GitHub

DNSViz: A DNS visualization tool

appliedmaterials.com

Updated: 2023-05-23 15:30:18 UTC (506 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

Secure (5)
  • appliedmaterials.com/A
  • appliedmaterials.com/MX
  • appliedmaterials.com/NS
  • appliedmaterials.com/SOA
  • appliedmaterials.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • appliedmaterials.com/DNSKEY (alg 13, id 28505)
  • appliedmaterials.com/DNSKEY (alg 13, id 32297)
  • appliedmaterials.com/DNSKEY (alg 13, id 49211)
  • appliedmaterials.com/DS (alg 13, id 32297)
  • appliedmaterials.com/DS (alg 13, id 32297)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 46551)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to appliedmaterials.com

NoticesNotices

Errors (1)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.228.79.201, UDP_-_EDNS0_512_D_KN)
Warnings (10)
  • ./DNSKEY (alg 8, id 20326): 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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 60955): 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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)
  • appliedmaterials.com/DS (alg 13, id 32297): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • appliedmaterials.com/DS (alg 13, id 32297): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • appliedmaterials.com/DS (alg 13, id 32297): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • appliedmaterials.com/DS (alg 13, id 32297): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • com/DS (alg 8, id 30909): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.228.79.201, UDP_-_EDNS0_4096_D_KN)
  • com/DS (alg 8, id 30909): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.228.79.201, UDP_-_EDNS0_4096_D_KN)
  • com/DS (alg 8, id 30909): 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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)
  • com/DS (alg 8, id 30909): 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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)

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