fdms.gov
Updated:
2021-07-15 13:00:53 UTC (1227 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- fdms.gov/A
- fdms.gov/AAAA
- fdms.gov/NS
- fdms.gov/SOA
- fdms.gov/SOA
- fdms.gov/SOA
- fdms.gov/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- fdms.gov/DNSKEY (alg 8, id 26340)
- fdms.gov/DNSKEY (alg 8, id 28851)
- fdms.gov/DNSKEY (alg 8, id 30228)
- fdms.gov/DNSKEY (alg 8, id 36078)
- fdms.gov/DNSKEY (alg 8, id 41551)
- fdms.gov/DS (alg 8, id 41551)
- fdms.gov/DS (alg 8, id 41551)
- gov/DNSKEY (alg 8, id 48498)
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to fdms.gov
Notices
Errors (13)
- fdms.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (134.67.12.12, 2620:117:506f:c::f00c)
- fdms.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (134.67.12.12, 2620:117:506f:c::f00c)
- fdms.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 2620:117:506f:c::f00c, UDP_-_NOEDNS_)
- fdms.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 2620:117:506f:c::f00c, UDP_-_NOEDNS_)
- fdms.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 2620:117:506f:c::f00c, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- fdms.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 2620:117:506f:c::f00c, UDP_-_NOEDNS_)
- fdms.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 2620:117:506f:c::f00c, TCP_-_NOEDNS_)
- fdms.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 2620:117:506f:c::f00c, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- fdms.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (134.67.12.12, 2620:117:506f:c::f00c, UDP_-_NOEDNS_)
- xcm0rketwh.fdms.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- fdms.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- fdms.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- fdms.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
- fdms.gov/DNSKEY (alg 8, id 30228): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (161.80.212.10, 161.80.212.12, 2620:117:5071:d4::f00a, 2620:117:5071:d4::f00c, UDP_-_EDNS0_4096_D_KN)
- fdms.gov/DNSKEY (alg 8, id 36078): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (134.67.12.10, 161.80.212.10, 2620:117:506f:c::f00a, 2620:117:5071:d4::f00a, UDP_-_EDNS0_4096_D_KN)
- fdms.gov/DS (alg 8, id 41551): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fdms.gov/DS (alg 8, id 41551): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fdms.gov/DS (alg 8, id 41551): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- fdms.gov/DS (alg 8, id 41551): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- xcm0rketwh.fdms.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- fdms.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- fdms.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
