fedex.com | DNSViz

fedex.com

Updated: 2023-03-07 10:31:31 UTC (626 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

Insecure (5)

fedex.com/A
fedex.com/MX
fedex.com/NS
fedex.com/SOA
fedex.com/TXT

Secure (2)

com/SOA
com/SOA

DNSKEY/DS/NSEC status

Secure (6)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 951)
NSEC3 proving non-existence of fedex.com/DS
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 36739)
com/DS (alg 8, id 30909)

Delegation status

Insecure (1)

com to fedex.com

Secure (1)

. to com

Notices

Errors (2)

fedex.com zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2620:119:4013:4:d2bf:9cff:fef1:c9e8)
fedex.com/SOA: The TCP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (2620:119:4013:4:d2bf:9cff:fef1:c9e8, TCP_-_EDNS0_4096_D_N)

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