View on GitHub

DNSViz: A DNS visualization tool

vwr.com

Updated: 2023-10-12 07:28:38 UTC (274 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC3 proving non-existence of vwr.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 4459)
  • com/DNSKEY (alg 8, id 63246)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • vwr.com zone: The following NS name(s) did not resolve to address(es): ns1.vwr.com
  • vwr.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (84.207.217.235)
  • vwr.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (84.207.217.235, UDP_-_NOEDNS_)
  • vwr.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (84.207.217.235, UDP_-_NOEDNS_)
Warnings (2)
  • com to vwr.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): b23.ns.els-gms.att.net, m23.ns.els-gms.att.net, ns10.vwr.com See RFC 1034, Sec. 4.2.2.
  • com to vwr.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns1.vwr.com, cbru.br.ns.els-gms.att.net, cmtu.mt.ns.els-gms.att.net 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