gps.gov
Updated:
2021-10-18 16:05:15 UTC (1132 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- gps.gov/A
- gps.gov/MX
- gps.gov/NS
- gps.gov/SOA
- gps.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gps.gov/DNSKEY (alg 5, id 17016)
- gps.gov/DNSKEY (alg 5, id 27093)
- gps.gov/DNSKEY (alg 5, id 27508)
- gps.gov/DS (alg 5, id 27508)
- gps.gov/DS (alg 5, id 27508)
Delegation status
Secure (2)
- . to gov
- gov to gps.gov
Notices
Warnings (22)
- RRSIG gps.gov/A alg 5, id 27093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/DNSKEY alg 5, id 27093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/DNSKEY alg 5, id 27093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/DNSKEY alg 5, id 27093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/DNSKEY alg 5, id 27508: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/DNSKEY alg 5, id 27508: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/DNSKEY alg 5, id 27508: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/MX alg 5, id 27093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/NS alg 5, id 27093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/SOA alg 5, id 27093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG gps.gov/TXT alg 5, id 27093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, UDP_-_EDNS0_4096_D_KN)
- gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, UDP_-_EDNS0_4096_D_KN)
- gps.gov/DS (alg 5, id 27508): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gps.gov/DS (alg 5, id 27508): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gps.gov/DS (alg 5, id 27508): 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.
- gps.gov/DS (alg 5, id 27508): 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.
- gps.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- gps.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- mqweubn9rd.gps.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- gps.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- gps.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
