View on GitHub
gatech.edu
Updated:
2025-04-13 08:39:09 UTC
(
347 days ago
)
Go to most recent »
« Previous analysis
|
Next analysis »
Tweet
DNSSEC
Responses
Servers
Analyze
DNSSEC options (
hide
)
|?|
RR types:
--All--
A
AAAA
TXT
PTR
MX
NS
SOA
CNAME
SRV
NAPTR
TLSA
NSEC3PARAM
CDNSKEY
CDS
CAA
|?|
DNSSEC algorithms:
--All--
1 - RSA/MD5
3 - DSA/SHA1
5 - RSA/SHA-1
6 - DSA-NSEC3-SHA1
7 - RSASHA1-NSEC3-SHA1
8 - RSA/SHA-256
10 - RSA/SHA-512
12 - GOST R 34.10-2001
13 - ECDSA Curve P-256 with SHA-256
14 - ECDSA Curve P-384 with SHA-384
15 - Ed25519
16 - Ed448
|?|
DS digest algorithms:
--All--
1 - SHA-1
2 - SHA-256
3 - GOST R 34.11-94
4 - SHA-384
|?|
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
Insecure
(5)
gatech.edu/A
gatech.edu/MX
gatech.edu/NS
gatech.edu/SOA
gatech.edu/TXT
Secure
(2)
edu/SOA
edu/SOA
DNSKEY/DS/NSEC status
Secure
(8)
./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 38696)
./DNSKEY (alg 8, id 53148)
NSEC3 proving non-existence of gatech.edu/DS
edu/DNSKEY (alg 13, id 35663)
edu/DNSKEY (alg 13, id 43203)
edu/DNSKEY (alg 13, id 57579)
edu/DS (alg 13, id 35663)
Delegation status
Insecure
(1)
edu to gatech.edu
Secure
(1)
. to edu
Notices
Errors
(18)
gatech.edu zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (168.24.2.35)
gatech.edu zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (168.24.2.35)
gatech.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (3.227.90.38)
gatech.edu/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.24.2.35, UDP_-_NOEDNS_)
gatech.edu/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.24.2.35, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
gatech.edu/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.24.2.35, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
gatech.edu/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.24.2.35, UDP_-_NOEDNS_)
gatech.edu/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (3.227.90.38, TCP_-_EDNS0_4096_D_N)
gatech.edu/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.24.2.35, TCP_-_NOEDNS_)
gatech.edu/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.24.2.35, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
gatech.edu/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.24.2.35, UDP_-_NOEDNS_)
gatech.edu/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
qvnz1.l5a7u.gatech.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
gatech.edu/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
gatech.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
gatech.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
gatech.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
gatech.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings
(1)
edu to gatech.edu: Authoritative AAAA records exist for dns1.gatech.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
DNSKEY legend
Full legend
SEP bit set
Revoke bit set
Trust anchor
See also
DNSSEC Debugger
by
Verisign Labs
.
Download:
png
|
svg
JavaScript is required to make the graph below interactive.