fedramp.gov
Updated:
2022-03-04 13:48:28 UTC (995 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- fedramp.gov/A
- fedramp.gov/MX
- fedramp.gov/NS
- fedramp.gov/NSEC3PARAM
- fedramp.gov/SOA
- fedramp.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- fedramp.gov/DNSKEY (alg 8, id 17109)
- fedramp.gov/DNSKEY (alg 8, id 3527)
- fedramp.gov/DS (alg 8, id 3527)
- fedramp.gov/DS (alg 8, id 3527)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to fedramp.gov
Notices
Errors (5)
- fedramp.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (159.142.150.68)
- fedramp.gov/SOA: The TCP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (159.142.150.68, TCP_-_EDNS0_4096_D_N)
- j20hwgxv5e.fedramp.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- fedramp.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- fedramp.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- fedramp.gov/DS (alg 8, id 3527): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fedramp.gov/DS (alg 8, id 3527): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fedramp.gov/DS (alg 8, id 3527): 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.
- fedramp.gov/DS (alg 8, id 3527): 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.
