View on GitHub

DNSViz: A DNS visualization tool

start-t.g2a.storebrand.no

Updated: 2023-02-16 16:10:21 UTC (520 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 (4)
  • g2a.storebrand.no/SOA
  • start-t.g2a.storebrand.no/NS
  • start-t.g2a.storebrand.no/SOA
  • storebrand.no/SOA
Secure (1)
  • no/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 storebrand.no/DS
  • no/DNSKEY (alg 13, id 38032)
  • no/DNSKEY (alg 13, id 47877)
  • no/DS (alg 13, id 38032)

Delegation statusDelegation status

Insecure (3)
  • g2a.storebrand.no to start-t.g2a.storebrand.no
  • no to storebrand.no
  • storebrand.no to g2a.storebrand.no
Secure (1)
  • . to no

NoticesNotices

Errors (1)
  • start-t.g2a.storebrand.no/NS: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (13.107.24.8, 13.107.160.8, 40.90.4.8, 64.4.48.8, 2603:1061:0:700::8, 2620:1ec:8ec:700::8, 2620:1ec:bda:700::8, 2a01:111:4000:700::8, UDP_-_EDNS0_4096_D_KN)
Warnings (2)
  • NSEC3 proving non-existence of storebrand.no/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of storebrand.no/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.

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