lps.gov

Updated: 2024-11-14 20:46:11 UTC (8 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

Secure (4)

lps.gov/MX
lps.gov/NS
lps.gov/SOA
lps.gov/TXT

DNSKEY/DS/NSEC status

Secure (13)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 61050)
gov/DNSKEY (alg 13, id 2536)
gov/DNSKEY (alg 13, id 35496)
gov/DS (alg 13, id 2536)
lps.gov/DNSKEY (alg 8, id 42364)
lps.gov/DNSKEY (alg 8, id 45791)
lps.gov/DNSKEY (alg 8, id 46425)
lps.gov/DNSKEY (alg 8, id 48208)
lps.gov/DS (alg 3, id 42364)
lps.gov/DS (alg 3, id 45791)
lps.gov/DS (alg 5, id 42364)
lps.gov/DS (alg 8, id 45791)

Non_existent (3)

lps.gov/DNSKEY (alg 3, id 42364)
lps.gov/DNSKEY (alg 3, id 45791)
lps.gov/DNSKEY (alg 5, id 42364)

Delegation status

Secure (2)

. to gov
gov to lps.gov

Notices

Errors (31)

gov to lps.gov: The DS RRset for the zone included algorithm 3 (DSA), but no DS RR matched a DNSKEY with algorithm 3 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
gov to lps.gov: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov zone: The following NS name(s) did not resolve to address(es): ns.lps.gov
lps.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (129.2.109.248)
lps.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (129.2.108.10)
lps.gov/DNSKEY (alg 8, id 42364): The DS RRset for the zone included algorithm 3 (DSA), but no RRSIG with algorithm 3 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/DNSKEY (alg 8, id 42364): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/DNSKEY (alg 8, id 45791): The DS RRset for the zone included algorithm 3 (DSA), but no RRSIG with algorithm 3 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/DNSKEY (alg 8, id 45791): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/DNSKEY (alg 8, id 46425): The DS RRset for the zone included algorithm 3 (DSA), but no RRSIG with algorithm 3 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/DNSKEY (alg 8, id 46425): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/DNSKEY (alg 8, id 48208): The DS RRset for the zone included algorithm 3 (DSA), but no RRSIG with algorithm 3 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/DNSKEY (alg 8, id 48208): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/MX: The DS RRset for the zone included algorithm 3 (DSA), but no RRSIG with algorithm 3 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
lps.gov/MX: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
lps.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (129.2.108.10, UDP_-_NOEDNS_)
lps.gov/NS: The DS RRset for the zone included algorithm 3 (DSA), but no RRSIG with algorithm 3 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/NS: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (129.2.109.248, TCP_-_EDNS0_4096_D_N)
lps.gov/SOA: The DS RRset for the zone included algorithm 3 (DSA), but no RRSIG with algorithm 3 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
lps.gov/SOA: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
lps.gov/TXT: The DS RRset for the zone included algorithm 3 (DSA), but no RRSIG with algorithm 3 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/TXT: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.2.109.248, UDP_-_EDNS0_4096_D_KN)
lps.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
lps.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
lps.gov/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
lps.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
lps.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
lps.gov/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
5yknh.7lz84.lps.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
lps.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (9)

gov to lps.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: ns.lps.gov See RFC 1034, Sec. 4.2.2.
lps.gov/DS (alg 3, id 42364): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
lps.gov/DS (alg 3, id 42364): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
lps.gov/DS (alg 3, id 42364): 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.
lps.gov/DS (alg 3, id 42364): 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.
lps.gov/DS (alg 3, id 45791): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
lps.gov/DS (alg 3, id 45791): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
lps.gov/DS (alg 3, id 45791): 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.
lps.gov/DS (alg 3, id 45791): 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.