View on GitHub

DNSViz: A DNS visualization tool

mytestsubdomain.pwa.network

Updated: 2020-03-24 16:39:38 UTC (1734 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 (2)
  • mytestsubdomain.pwa.network/CNAME
  • webapps.seattleclouds.com/A
Secure (3)
  • com/SOA
  • com/SOA
  • network/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of pwa.network/DS
  • NSEC3 proving non-existence of seattleclouds.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 56311)
  • com/DS (alg 8, id 30909)
  • network/DNSKEY (alg 8, id 35385)
  • network/DNSKEY (alg 8, id 42646)
  • network/DS (alg 8, id 42646)
  • network/DS (alg 8, id 42646)

Delegation statusDelegation status

Insecure (2)
  • com to seattleclouds.com
  • network to pwa.network
Secure (2)
  • . to com
  • . to network

NoticesNotices

Errors (2)
  • NSEC3 proving non-existence of pwa.network/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of pwa.network/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (9)
  • NSEC3 proving non-existence of pwa.network/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of pwa.network/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • com to seattleclouds.com: Authoritative AAAA records exist for ns-465.awsdns-58.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • network/DS (alg 8, id 42646): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • network/DS (alg 8, id 42646): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • network/DS (alg 8, id 42646): 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.
  • network/DS (alg 8, id 42646): 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.
  • webapps.seattleclouds.com/A: 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. (205.251.195.180, UDP_-_EDNS0_4096_D_Ks)
  • webapps.seattleclouds.com/A: 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. (205.251.193.209, UDP_-_EDNS0_4096_D_Ks)

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