tamu.edu

Updated: 2023-02-22 18:42:30 UTC (641 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 (5)

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

DNSKEY/DS/NSEC status

Secure (17)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 951)
edu/DNSKEY (alg 8, id 28065)
edu/DNSKEY (alg 8, id 34085)
edu/DS (alg 8, id 28065)
tamu.edu/DNSKEY (alg 5, id 21870)
tamu.edu/DNSKEY (alg 5, id 30274)
tamu.edu/DNSKEY (alg 5, id 32956)
tamu.edu/DNSKEY (alg 5, id 55857)
tamu.edu/DNSKEY (alg 8, id 33378)
tamu.edu/DNSKEY (alg 8, id 43116)
tamu.edu/DNSKEY (alg 8, id 54682)
tamu.edu/DS (alg 5, id 30274)
tamu.edu/DS (alg 5, id 30274)
tamu.edu/DS (alg 8, id 53134)
tamu.edu/DS (alg 8, id 54682)
tamu.edu/DS (alg 8, id 54682)

Non_existent (1)

tamu.edu/DNSKEY (alg 8, id 53134)

Delegation status

Secure (2)

. to edu
edu to tamu.edu

Notices

Errors (3)

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_)

Warnings (39)

RRSIG tamu.edu/A alg 5, id 55857: 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 30274: 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 30274: 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 30274: 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 30274: 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 30274: 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 30274: 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 30274: 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 32956: 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 32956: 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 32956: 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 32956: 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 32956: 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 32956: 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 32956: 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 55857: 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 55857: 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 55857: 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 55857: 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 55857: 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 55857: 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 55857: 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 55857: 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 55857: 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 55857: 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 55857: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
tamu.edu/DS (alg 5, id 30274): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tamu.edu/DS (alg 5, id 30274): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tamu.edu/DS (alg 5, id 30274): 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 5, id 30274): 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.
v47qrtspiu.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.