srs.gov
Updated:
2023-12-15 23:58:10 UTC (343 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- srs.gov/MX
- srs.gov/NS
- srs.gov/NSEC3PARAM
- srs.gov/NSEC3PARAM (NODATA)
- srs.gov/SOA
- srs.gov/SOA
- srs.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (3)
- srs.gov/DNSKEY (alg 8, id 30052)
- srs.gov/DNSKEY (alg 8, id 38853)
- srs.gov/DNSKEY (alg 8, id 3891)
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC proving non-existence of srs.gov/DS
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 49735)
- gov/DNSKEY (alg 8, id 64280)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 64280)
Delegation status
Insecure (1)
- gov to srs.gov
Secure (1)
- . to gov
Notices
Errors (11)
- srs.gov/DNSKEY (alg 8, id 38853): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (192.188.22.22, 192.188.22.52, 2001:400:ffff:ffff:ffff::4444, 2001:400:ffff:ffff:ffff::8052, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- srs.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (192.188.22.22, 192.188.22.52, 2001:400:ffff:ffff:ffff::4444, 2001:400:ffff:ffff:ffff::8052, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- srs.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (192.188.22.22, 192.188.22.52, 2001:400:ffff:ffff:ffff::4444, 2001:400:ffff:ffff:ffff::8052, UDP_-_EDNS0_4096_D_KN)
- srs.gov/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (192.188.22.22, 192.188.22.52, 2001:400:ffff:ffff:ffff::4444, 2001:400:ffff:ffff:ffff::8052, UDP_-_EDNS0_4096_D_KN)
- srs.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (192.188.22.22, 192.188.22.52, 2001:400:ffff:ffff:ffff::4444, 2001:400:ffff:ffff:ffff::8052, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- srs.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (192.188.22.22, 192.188.22.52, 2001:400:ffff:ffff:ffff::4444, 2001:400:ffff:ffff:ffff::8052, UDP_-_EDNS0_4096_D_KN)
- srs.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- srs.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- la96j471u0.srs.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- srs.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- srs.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- srs.gov/DNSKEY (alg 8, id 30052): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (192.188.22.22, 192.188.22.52, 2001:400:ffff:ffff:ffff::4444, 2001:400:ffff:ffff:ffff::8052, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- srs.gov/DNSKEY (alg 8, id 3891): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (192.188.22.22, 192.188.22.52, 2001:400:ffff:ffff:ffff::4444, 2001:400:ffff:ffff:ffff::8052, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- srs.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- srs.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- srs.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- la96j471u0.srs.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
