View on GitHub

DNSViz: A DNS visualization tool

federalregister.gov

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

RRset statusRRset status

Bogus (3)
  • federalregister.gov/NS
  • federalregister.gov/NSEC3PARAM (NODATA)
  • federalregister.gov/SOA
Secure (6)
  • federalregister.gov/A
  • federalregister.gov/NS
  • federalregister.gov/NSEC3PARAM
  • federalregister.gov/SOA
  • federalregister.gov/TXT
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (3)
  • NSEC proving non-existence of federalregister.gov/NSEC3PARAM
  • federalregister.gov/DNSKEY (alg 13, id 2371)
  • federalregister.gov/DNSKEY (alg 13, id 34505)
Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC3 proving non-existence of federalregister.gov/DS
  • federalregister.gov/DNSKEY (alg 8, id 21955)
  • federalregister.gov/DNSKEY (alg 8, id 35838)
  • federalregister.gov/DNSKEY (alg 8, id 9636)
  • federalregister.gov/DS (alg 8, id 21955)
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 40921)
  • gov/DNSKEY (alg 8, id 49735)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 64280)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to federalregister.gov

NoticesNotices

Errors (44)
  • NSEC proving non-existence of federalregister.gov/NSEC3PARAM: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of federalregister.gov/NSEC3PARAM: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of federalregister.gov/NSEC3PARAM: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of federalregister.gov/NSEC3PARAM: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of federalregister.gov/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: federalregister.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of federalregister.gov/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: federalregister.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC3 proving non-existence of federalregister.gov/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 federalregister.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG federalregister.gov/TXT alg 13, id 34505: The TTL of the RRset (28800) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG federalregister.gov/TXT alg 13, id 34505: The TTL of the RRset (28800) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • federalregister.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (75.2.36.59, 99.83.174.136)
  • federalregister.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (75.2.36.59, 99.83.174.136, UDP_-_NOEDNS_)
  • federalregister.gov/A: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/A: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/A: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/DNSKEY (alg 13, id 2371): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • federalregister.gov/DNSKEY (alg 13, id 2371): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • federalregister.gov/DNSKEY (alg 13, id 34505): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/DNSKEY (alg 13, id 34505): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • federalregister.gov/DNSKEY (alg 13, id 34505): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • federalregister.gov/DNSKEY (alg 8, id 21955): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • federalregister.gov/DNSKEY (alg 8, id 21955): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/DNSKEY (alg 8, id 35838): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/DNSKEY (alg 8, id 9636): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • federalregister.gov/DNSKEY (alg 8, id 9636): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (75.2.36.59, 99.83.174.136, UDP_-_NOEDNS_)
  • federalregister.gov/NS: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/NS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/NS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/NSEC3PARAM: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/SOA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • federalregister.gov/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • federalregister.gov/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • federalregister.gov/TXT: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/TXT: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/TXT: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN)
  • gov to federalregister.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to federalregister.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • federalregister.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • o654lbshjy.federalregister.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • federalregister.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • federalregister.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • federalregister.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • federalregister.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • NSEC3 proving non-existence of federalregister.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of federalregister.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • federalregister.gov/DNSKEY (alg 13, id 2371): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/DNSKEY (alg 8, id 35838): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.159.4.127, 162.159.5.58, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to federalregister.gov: The glue address(es) for ns1.federalregister.gov (162.159.4.127) differed from its authoritative address(es) (75.2.36.59, 99.83.174.136). See RFC 1034, Sec. 4.2.2.
  • gov to federalregister.gov: The glue address(es) for ns2.federalregister.gov (162.159.5.58) differed from its authoritative address(es) (75.2.36.59, 99.83.174.136). See RFC 1034, Sec. 4.2.2.
  • gov/DNSKEY (alg 8, id 40921): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (69.36.153.30, 69.36.157.30, 81.19.194.30, 209.112.123.30, 2001:500:4431::2:30, 2620:74:27::2:30, 2620:74:28::2:30, 2620:74:29::2:30, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • federalregister.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • federalregister.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • federalregister.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • o654lbshjy.federalregister.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • federalregister.gov/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