tamu.edu

Updated: 2023-04-23 05:08:17 UTC (582 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 (5)

tamu.edu/A
tamu.edu/MX
tamu.edu/NS
tamu.edu/SOA
tamu.edu/TXT

DNSKEY/DS/NSEC status

Bogus (4)

tamu.edu/DNSKEY (alg 8, id 27858)
tamu.edu/DNSKEY (alg 8, id 34975)
tamu.edu/DNSKEY (alg 8, id 37341)
tamu.edu/DNSKEY (alg 8, id 54682)

Secure (12)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 60955)
edu/DNSKEY (alg 8, id 28065)
edu/DNSKEY (alg 8, id 30503)
edu/DS (alg 8, id 28065)
tamu.edu/DS (alg 5, id 30274)
tamu.edu/DS (alg 8, id 34975)
tamu.edu/DS (alg 8, id 34975)
tamu.edu/DS (alg 8, id 35167)
tamu.edu/DS (alg 8, id 53134)
tamu.edu/DS (alg 8, id 54682)
tamu.edu/DS (alg 8, id 54682)

Non_existent (4)

tamu.edu/DNSKEY (alg 5, id 30274)
tamu.edu/DNSKEY (alg 5, id 57030)
tamu.edu/DNSKEY (alg 8, id 35167)
tamu.edu/DNSKEY (alg 8, id 53134)

Delegation status

Bogus (1)

edu to tamu.edu

Secure (1)

. to edu

Notices

Errors (23)

RRSIG tamu.edu/DNSKEY alg 8, id 34975: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 34975: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 34975: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 34975: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 37341: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 37341: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 37341: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 37341: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 54682: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 54682: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 54682: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/DNSKEY alg 8, id 54682: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG tamu.edu/SOA alg 8, id 37341: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
edu to tamu.edu: 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. (128.194.211.238, 192.195.87.5, 192.195.94.166, TCP_-_EDNS0_4096_D_KN)
edu to tamu.edu: 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. (128.194.211.238, 192.195.87.5, 192.195.94.166, TCP_-_EDNS0_4096_D_KN)
tamu.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (165.91.16.133)
tamu.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (165.91.16.133, UDP_-_NOEDNS_)
tamu.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (165.91.16.133, UDP_-_NOEDNS_)
tamu.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
1dfcnu753o.tamu.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
tamu.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
tamu.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
tamu.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (26)

RRSIG tamu.edu/A alg 5, id 57030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG tamu.edu/DNSKEY alg 5, id 57030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG tamu.edu/DNSKEY alg 5, id 57030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG tamu.edu/DNSKEY alg 5, id 57030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG tamu.edu/DNSKEY alg 5, id 57030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG tamu.edu/MX alg 5, id 57030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG tamu.edu/NS alg 5, id 57030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG tamu.edu/SOA alg 5, id 57030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG tamu.edu/TXT alg 5, id 57030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
tamu.edu/DS (alg 8, id 34975): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tamu.edu/DS (alg 8, id 34975): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tamu.edu/DS (alg 8, id 34975): 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.
tamu.edu/DS (alg 8, id 34975): 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.
tamu.edu/DS (alg 8, id 35167): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tamu.edu/DS (alg 8, id 35167): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tamu.edu/DS (alg 8, id 35167): 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.
tamu.edu/DS (alg 8, id 35167): 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.
tamu.edu/DS (alg 8, id 54682): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tamu.edu/DS (alg 8, id 54682): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tamu.edu/DS (alg 8, id 54682): 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.
tamu.edu/DS (alg 8, id 54682): 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.
tamu.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
1dfcnu753o.tamu.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
tamu.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
tamu.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
tamu.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.