pms.psc.gov

Updated: 2021-08-25 18:15:25 UTC (1137 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (1)

pms.ha.psc.gov/A

Secure (1)

pms.psc.gov/CNAME

DNSKEY/DS/NSEC status

Bogus (3)

ha.psc.gov/DNSKEY (alg 7, id 180)
ha.psc.gov/DNSKEY (alg 7, id 21380)
ha.psc.gov/DNSKEY (alg 7, id 27248)

Secure (15)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26838)
gov/DNSKEY (alg 8, id 57735)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)
ha.psc.gov/DS (alg 7, id 180)
ha.psc.gov/DS (alg 7, id 39093)
psc.gov/DNSKEY (alg 8, id 14656)
psc.gov/DNSKEY (alg 8, id 16668)
psc.gov/DNSKEY (alg 8, id 5095)
psc.gov/DNSKEY (alg 8, id 51397)
psc.gov/DS (alg 8, id 14656)
psc.gov/DS (alg 8, id 14656)
psc.gov/DS (alg 8, id 51397)
psc.gov/DS (alg 8, id 51397)

Non_existent (1)

ha.psc.gov/DNSKEY (alg 7, id 39093)

Delegation status

Bogus (1)

psc.gov to ha.psc.gov

Secure (2)

. to gov
gov to psc.gov

Notices

Errors (7)

ha.psc.gov/DNSKEY (alg 7, id 21380): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (156.40.55.100, UDP_-_EDNS0_4096_D_KN)
ha.psc.gov/DNSKEY (alg 7, id 27248): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (165.112.13.50, UDP_-_EDNS0_4096_D_KN)
pms.psc.gov/CNAME: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (158.74.30.99, UDP_-_EDNS0_4096_)
pms.psc.gov/CNAME: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (158.74.30.99, UDP_-_EDNS0_4096_D_KN)
pms.psc.gov/CNAME: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (158.74.30.99, UDP_-_EDNS0_4096_D_KN)
psc.gov to ha.psc.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (156.40.55.100, 165.112.13.50, UDP_-_EDNS0_4096_D_KN)
pms.psc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (22)

RRSIG ha.psc.gov/DNSKEY alg 7, id 180: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 180: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 180: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 180: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 21380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 21380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 27248: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG ha.psc.gov/DNSKEY alg 7, id 27248: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG pms.ha.psc.gov/A alg 7, id 21380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG pms.ha.psc.gov/A alg 7, id 27248: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
ha.psc.gov/DS (alg 7, id 180): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ha.psc.gov/DS (alg 7, id 180): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ha.psc.gov/DS (alg 7, id 180): 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.
ha.psc.gov/DS (alg 7, id 180): 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.
psc.gov/DS (alg 8, id 14656): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
psc.gov/DS (alg 8, id 14656): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
psc.gov/DS (alg 8, id 14656): 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.
psc.gov/DS (alg 8, id 14656): 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.
psc.gov/DS (alg 8, id 51397): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
psc.gov/DS (alg 8, id 51397): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
psc.gov/DS (alg 8, id 51397): 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.
psc.gov/DS (alg 8, id 51397): 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.