pg.com | DNSViz

pg.com

Updated: 2023-03-23 21:19:05 UTC (608 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Insecure (5)

pg.com/A
pg.com/MX
pg.com/NS
pg.com/SOA
pg.com/TXT

Secure (2)

com/SOA
com/SOA

DNSKEY/DS/NSEC status

Secure (7)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 60955)
./DNSKEY (alg 8, id 951)
NSEC3 proving non-existence of pg.com/DS
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 36739)
com/DS (alg 8, id 30909)

Delegation status

Insecure (1)

com to pg.com

Secure (1)

. to com

Notices

Warnings (2)

com to pg.com: The glue address(es) for ns1-05.azure-dns.com (40.90.4.5) differed from its authoritative address(es) (13.107.236.5). See RFC 1034, Sec. 4.2.2.
pg.com/SOA: The case of the query name (pg.com) was not preserved in the Question section of the response. (150.171.21.5, UDP_-_EDNS0_4096_D_KN)

DNSKEY legend

Full legend

	SEP bit set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph