pgecorp.com
Updated:
2024-09-04 16:33:46 UTC (77 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- pgecorp.com/A
- pgecorp.com/NS
- pgecorp.com/SOA
- pgecorp.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of pgecorp.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 59354)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to pgecorp.com
Secure (1)
- . to com
Notices
Errors (4)
- pgecorp.com zone: The following NS name(s) did not resolve to address(es): can13.pge.com, can14.pge.com
- pgecorp.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (131.90.0.50, 131.90.0.51)
- pgecorp.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (131.90.0.50, 131.90.0.51, UDP_-_NOEDNS_)
- pgecorp.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (131.90.0.50, 131.90.0.51, UDP_-_NOEDNS_)
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.
JavaScript is required to make the graph below interactive.
