View on GitHub

DNSViz: A DNS visualization tool

pgecorp.com

« 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 (4)
  • pgecorp.com/A
  • pgecorp.com/NS
  • pgecorp.com/SOA
  • pgecorp.com/TXT
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • NSEC3 proving non-existence of pgecorp.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 32298)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Insecure (1)
  • com to pgecorp.com
Secure (1)
  • . to com

NoticesNotices

Errors (14)
  • pgecorp.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51)
  • pgecorp.com zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51)
  • pgecorp.com/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN)
  • pgecorp.com/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • pgecorp.com/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN)
  • pgecorp.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, TCP_-_EDNS0_4096_D_N)
  • pgecorp.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • pgecorp.com/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN)
  • pgecorp.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • pgecorp.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • pgecorp.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • pgecorp.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • pgecorp.com/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • n89txqukwa.pgecorp.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
  • com to pgecorp.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ns3.pge.com, ns4.pge.com See RFC 1034, Sec. 4.2.2.
  • com to pgecorp.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: can13.pge.com, can14.pge.com 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