_25._tcp.mx.runbox.com | DNSViz

_25._tcp.mx.runbox.com

Recursive analysis

Updated (recursive): 2021-02-06 06:10:10 UTC (1415 days ago) Go to delegated analysis »

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 (2)

_25._tcp.mx.runbox.com/TLSA (NODATA)
runbox.com/SOA

DNSKEY/DS/NSEC status

Secure (10)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 42351)
NSEC proving non-existence of _25._tcp.mx.runbox.com/TLSA
NSEC proving non-existence of _25._tcp.mx.runbox.com/TLSA
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 58540)
com/DS (alg 8, id 30909)
runbox.com/DNSKEY (alg 13, id 12629)
runbox.com/DNSKEY (alg 13, id 4332)
runbox.com/DS (alg 13, id 4332)

Delegation status

Secure (2)

. to com
com to runbox.com

Notices

Errors (2)

NSEC proving non-existence of _25._tcp.mx.runbox.com/TLSA: No NSEC RR matches the SNAME (_25._tcp.mx.runbox.com). See RFC 4035, Sec. 3.1.3.1.
NSEC proving non-existence of _25._tcp.mx.runbox.com/TLSA: No NSEC RR matches the SNAME (_25._tcp.mx.runbox.com). See RFC 4035, Sec. 3.1.3.1.

DNSKEY legend

Full legend

	SEP bit set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph