gsa.gov
Updated:
2022-03-04 20:34:57 UTC (844 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- gsa.gov/A
- gsa.gov/AAAA
- gsa.gov/MX
- gsa.gov/NS
- gsa.gov/NSEC3PARAM
- gsa.gov/SOA
- gsa.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gsa.gov/DNSKEY (alg 8, id 10039)
- gsa.gov/DNSKEY (alg 8, id 60450)
- gsa.gov/DS (alg 8, id 10039)
- gsa.gov/DS (alg 8, id 10039)
Delegation status
Secure (2)
- . to gov
- gov to gsa.gov
Notices
Errors (6)
- gsa.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (159.142.150.68)
- gsa.gov/DS (alg 8, id 10039): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gsa.gov/DS (alg 8, id 10039): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gsa.gov/SOA: The TCP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (159.142.150.68, TCP_-_EDNS0_4096_D_N)
- gsa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- y1ergzvlik.gsa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- gsa.gov/DS (alg 8, id 10039): 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.
- gsa.gov/DS (alg 8, id 10039): 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.
JavaScript is required to make the graph below interactive.
