View on GitHub

DNSViz: A DNS visualization tool

facebook.de

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (6)
  • facebook.de/A
  • facebook.de/AAAA
  • facebook.de/NS
  • facebook.de/SOA
  • facebook.de/SOA
  • facebook.de/TXT
Secure (1)
  • de/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • NSEC3 proving non-existence of facebook.de/DS
  • de/DNSKEY (alg 8, id 26755)
  • de/DNSKEY (alg 8, id 54729)
  • de/DS (alg 8, id 26755)

Delegation statusDelegation status

Insecure (1)
  • de to facebook.de
Secure (1)
  • . to de

NoticesNotices

Errors (7)
  • NSEC3 proving non-existence of facebook.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of facebook.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • facebook.de zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.89.218.12)
  • facebook.de zone: There was an error resolving the following NS name(s) to address(es): a.ns.facebook.com
  • facebook.de/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.89.218.12, UDP_-_NOEDNS_)
  • facebook.de/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.89.218.12, 2a03:2880:f0fd:c:face:b00c:0:35, UDP_-_NOEDNS_)
  • facebook.de/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • ./DNSKEY (alg 8, id 14748): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:7fd::1, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:7fd::1, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 26838): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:7fd::1, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of facebook.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of facebook.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • de/DS (alg 8, id 26755): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:7fd::1, UDP_-_EDNS0_4096_D_KN)
  • de/DS (alg 8, id 26755): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:7fd::1, UDP_-_EDNS0_4096_D_KN)
  • facebook.de/A: 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. (2a03:2880:f0fd:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
  • facebook.de/NS: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2a03:2880:f1fc:c:face:b00c:0:35, UDP_-_EDNS0_4096_D_KN)
  • facebook.de/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph