verizon.com
Updated:
2022-07-21 00:01:26 UTC (860 days ago)
Go to most recent »
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 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of verizon.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 32298)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to verizon.com
Secure (1)
- . to com
Notices
Warnings (3)
- 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 8, id 30909): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- com/DS (alg 8, id 30909): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
