congressionalrecord.gov
Updated:
2022-08-31 14:35:49 UTC (813 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- congressionalrecord.gov/A
- congressionalrecord.gov/AAAA
- congressionalrecord.gov/NS
- congressionalrecord.gov/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- congressionalrecord.gov/DNSKEY (alg 13, id 2371)
- congressionalrecord.gov/DNSKEY (alg 13, id 34505)
- congressionalrecord.gov/DS (alg 13, id 2371)
- gov/DNSKEY (alg 8, id 261)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to congressionalrecord.gov
Notices
Warnings (3)
- gov to congressionalrecord.gov: Authoritative AAAA records exist for ns1.congressionalrecord.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to congressionalrecord.gov: Authoritative AAAA records exist for ns2.congressionalrecord.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to congressionalrecord.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: chip.ns.cloudflare.com, cruz.ns.cloudflare.com See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
