fdsys.gov
Updated:
2021-08-12 13:24:55 UTC (1198 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- fdsys.gov/A
- fdsys.gov/NS
- fdsys.gov/NSEC3PARAM
- fdsys.gov/NSEC3PARAM
- fdsys.gov/NSEC3PARAM (NODATA)
- fdsys.gov/SOA
- fdsys.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- fdsys.gov/DNSKEY (alg 8, id 17551)
- fdsys.gov/DNSKEY (alg 8, id 20076)
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- NSEC3 proving non-existence of fdsys.gov/DS
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to fdsys.gov
Secure (1)
- . to gov
Notices
Errors (14)
- NSEC3 proving non-existence of fdsys.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 fdsys.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- fdsys.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_4096_D_KN)
- fdsys.gov/DNSKEY (alg 8, id 20076): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- fdsys.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_4096_D_KN)
- fdsys.gov/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_4096_D_KN)
- fdsys.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.64.100, 162.140.252.180, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- fdsys.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_4096_D_KN)
- fdsys.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- fdsys.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- fdsys.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- fdsys.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- 3lwno1uib6.fdsys.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- fdsys.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
- NSEC3 proving non-existence of fdsys.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of fdsys.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- fdsys.gov/DNSKEY (alg 8, id 17551): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.64.100, 162.140.252.180, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- gov to fdsys.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns1.gpo.gov, ns2.gpo.gov See RFC 1034, Sec. 4.2.2.
- fdsys.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- fdsys.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- fdsys.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 3lwno1uib6.fdsys.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- fdsys.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
