verizon.com
Updated:
2024-07-24 19:04:50 UTC (2 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- verizon.com/A
- verizon.com/MX
- verizon.com/NS
- verizon.com/SOA
- verizon.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 verizon.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 verizon.com
Secure (1)
- . to com
Notices
Warnings (4)
- ./DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_512_D_KN)
- 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.
- com/DS (alg 13, id 19718): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- com/DS (alg 13, id 19718): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
