View on GitHub

DNSViz: A DNS visualization tool

newfield.com

Updated: 2023-10-03 20:19:04 UTC (about a year ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (show)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • newfield.com/A
  • newfield.com/NS
  • newfield.com/NSEC3PARAM
  • newfield.com/NSEC3PARAM
  • newfield.com/SOA
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • newfield.com/DNSKEY (alg 10, id 17807)
  • newfield.com/DNSKEY (alg 10, id 6246)
Secure (7)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC3 proving non-existence of newfield.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 4459)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

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

NoticesNotices

Errors (5)
  • newfield.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • newfield.com/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • newfield.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • newfield.com/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • 46du1i7s9o.newfield.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (25)
  • RRSIG newfield.com/A alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/A alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/DNSKEY alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/DNSKEY alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/DNSKEY alg 10, id 6246: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/DNSKEY alg 10, id 6246: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/DNSKEY alg 10, id 6246: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/DNSKEY alg 10, id 6246: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/NS alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/NS alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/NSEC3PARAM alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/NSEC3PARAM alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/NSEC3PARAM alg 10, id 17807: The value of the Signature Inception field of the RRSIG RR (2023-10-03 20:19:03+00:00) is within possible clock skew range (1 second) of the current time (2023-10-03 20:19:04+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG newfield.com/SOA alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/SOA alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/SOA alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/SOA alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG newfield.com/SOA alg 10, id 17807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • com to newfield.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: ns2.ovintiv.com See RFC 1034, Sec. 4.2.2.
  • newfield.com/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • newfield.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • newfield.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 46du1i7s9o.newfield.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • newfield.com/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • newfield.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Mouse over and click elements in the graph below to see more detail.
Created with Raphaël 2.1.2.(2023-10-03 16:37:30 UTC)com(2023-10-03 18:13:34 UTC)newfield.com(2023-10-03 20:19:04 UTC)DNSKEYalg=8, id=110192048 bitsDNSKEYalg=8, id=203262048 bitsDNSKEYalg=8, id=467802048 bitsDSdigest alg=2 NSEC3com/SOAcom/SOADNSKEYalg=8, id=309092048 bitsDNSKEYalg=8, id=44591280 bitsnewfield.com/SOAnewfield.com/Anewfield.com/NSnewfield.com/NSEC3PARAMnewfield.com/NSEC3PARAMDNSKEYalg=10, id=178071024 bitsDNSKEYalg=10, id=62462048 bits