View on GitHub

DNSViz: A DNS visualization tool

mastercard.com

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • mastercard.com/A
  • mastercard.com/MX
  • mastercard.com/NS
  • mastercard.com/SOA
  • mastercard.com/TXT
Secure (1)
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

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

Delegation statusDelegation status

Insecure (1)
  • com to mastercard.com
Secure (1)
  • . to com

NoticesNotices

Errors (3)
  • mastercard.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:3c00:6414:4::53)
  • mastercard.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:3c00:6414:4::53, UDP_-_NOEDNS_)
  • mastercard.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:3c00:6414:4::53, UDP_-_NOEDNS_)
Warnings (2)
  • com to mastercard.com: Authoritative AAAA records exist for dns1.mastercard.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • com to mastercard.com: Authoritative AAAA records exist for dns2.mastercard.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph