srs.gov
Updated:
2022-07-26 11:13:01 UTC (852 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- srs.gov/MX
- srs.gov/NS
- srs.gov/SOA
- srs.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of srs.gov/DS
- gov/DNSKEY (alg 8, id 261)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to srs.gov
Secure (1)
- . to gov
Notices
Errors (4)
- NSEC3 proving non-existence of srs.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of srs.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- srs.gov zone: The following NS name(s) resolved to IP address(es) in private IP address space: ns1.srs.gov
- srs.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- NSEC3 proving non-existence of srs.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of srs.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- gov to srs.gov: The glue address(es) for ns1.srs.gov (192.33.240.10) differed from its authoritative address(es) (192.33.240.10, 192.168.7.17). See RFC 1034, Sec. 4.2.2.
- srs.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
