twitter.com
Updated:
2023-03-22 05:02:27 UTC (408 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (12)
- twitter.com/A
- twitter.com/A
- twitter.com/A
- twitter.com/A
- twitter.com/A
- twitter.com/A
- twitter.com/A
- twitter.com/A
- twitter.com/MX
- twitter.com/NS
- twitter.com/SOA
- twitter.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 951)
- NSEC3 proving non-existence of twitter.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 twitter.com
Secure (1)
- . to com
Notices
Warnings (2)
- com to twitter.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): ns1.p34.dynect.net, ns2.p34.dynect.net, ns4.p34.dynect.net, ns3.p34.dynect.net
- twitter.com/TXT: 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. (2600:2000:2210::34, 2600:2000:2220::34, 2600:2000:2230::34, 2600:2000:2240::34, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
