chase.com | DNSViz

chase.com

Updated: 2023-01-18 14:02:51 UTC (684 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 (6)

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

Secure (2)

com/SOA
com/SOA

DNSKEY/DS/NSEC status

Secure (7)

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

Delegation status

Insecure (1)

com to chase.com

Secure (1)

. to com

Notices

Errors (1)

chase.com zone: The following NS name(s) did not resolve to address(es): dns159650ex02.amer.ddi.jpmchase.net, dns159650ex03.amer.ddi.jpmchase.net, dns159650ex04.amer.ddi.jpmchase.net, dns159651ex01.amer.ddi.jpmchase.net, dns159651ex03.amer.ddi.jpmchase.net, dns159651ex04.amer.ddi.jpmchase.net, dns159932ex01.amer.ddi.jpmchase.net

Warnings (1)

com to chase.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): dns159651ex04.amer.ddi.jpmchase.net, dns159650ex02.amer.ddi.jpmchase.net, dns159651ex01.amer.ddi.jpmchase.net, dns159932ex01.amer.ddi.jpmchase.net, dns159651ex03.amer.ddi.jpmchase.net, dns159650ex03.amer.ddi.jpmchase.net, dns159650ex04.amer.ddi.jpmchase.net 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

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph