verizon.com | DNSViz

verizon.com

Updated: 2022-04-26 18:10:06 UTC (946 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)

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

Secure (3)

com/SOA
com/SOA
com/SOA

DNSKEY/DS/NSEC status

Secure (6)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 47671)
NSEC3 proving non-existence of verizon.com/DS
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 37269)
com/DS (alg 8, id 30909)

Delegation status

Insecure (1)

com to verizon.com

Secure (1)

. to com

Notices

Errors (1)

com/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:7fe::53, UDP_-_NOEDNS_)

Warnings (1)

com to verizon.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): s2ns2.verizon.com, s1ns1.verizon.com, s4ns4.verizon.com, s3ns3.verizon.com See RFC 1034, Sec. 4.2.2.

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