tamu.edu

Updated: 2024-07-30 18:29:12 UTC (116 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 (16)

./DNSKEY (alg 8, id 20038)
./DNSKEY (alg 8, id 20326)
edu/DNSKEY (alg 13, id 30299)
edu/DNSKEY (alg 13, id 35663)
edu/DS (alg 13, id 35663)
tamu.edu/DNSKEY (alg 8, id 28746)
tamu.edu/DNSKEY (alg 8, id 33279)
tamu.edu/DNSKEY (alg 8, id 34975)
tamu.edu/DNSKEY (alg 8, id 38601)
tamu.edu/DNSKEY (alg 8, id 43741)
tamu.edu/DS (alg 8, id 28135)
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 43741)
tamu.edu/DS (alg 8, id 43741)

Non_existent (2)

tamu.edu/DNSKEY (alg 8, id 28135)
tamu.edu/DNSKEY (alg 8, id 35167)

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. (192.195.87.5)
tamu.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.195.87.5, UDP_-_NOEDNS_)
tamu.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.195.87.5, UDP_-_NOEDNS_)

Warnings (14)

edu to tamu.edu: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu zone): ns4.tamu.edu See RFC 1034, Sec. 4.2.2.
edu to tamu.edu: The glue address(es) for ns3.tamu.edu (192.195.87.5) differed from its authoritative address(es) (66.64.83.4). See RFC 1034, Sec. 4.2.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): 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 43741): 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 43741): 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 43741): 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 43741): 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.