View on GitHub

DNSViz: A DNS visualization tool

_25._tcp.nist-gov.mail.protection.outlook.com

Updated: 2020-12-25 23:12:15 UTC (1457 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 (7)
  • _tcp.nist-gov.mail.protection.outlook.com/NS (NXDOMAIN)
  • nist-gov.mail.protection.outlook.com/A
  • nist-gov.mail.protection.outlook.com/AAAA
  • outlook.com/SOA
  • outlook.com/SOA
  • outlook.com/SOA
  • protection.outlook.com/SOA
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC3 proving non-existence of outlook.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 31510)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Insecure (3)
  • com to outlook.com
  • outlook.com to protection.outlook.com
  • protection.outlook.com to mail.protection.outlook.com
Secure (1)
  • . to com

NoticesNotices

Errors (4)
  • _25._tcp.nist-gov.mail.protection.outlook.com/TLSA: The response had an invalid RCODE (NOTIMP). See RFC 1035, Sec. 4.1.1. (104.47.67.17, 104.47.68.17, 104.47.118.145, 104.47.118.177, UDP_-_NOEDNS_)
  • _tcp.nist-gov.mail.protection.outlook.com/NS (NXDOMAIN): The NXDOMAIN response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (104.47.67.17, 104.47.68.17, 104.47.118.145, 104.47.118.177, UDP_-_NOEDNS_)
  • mail.protection.outlook.com/DNSKEY: The response had an invalid RCODE (NOTIMP). See RFC 1035, Sec. 4.1.1. (104.47.67.17, 104.47.68.17, 104.47.118.145, 104.47.118.177, UDP_-_NOEDNS_)
  • mail.protection.outlook.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • _tcp.nist-gov.mail.protection.outlook.com/NS (NXDOMAIN): The response had an invalid RCODE (FORMERR) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (104.47.67.17, 104.47.68.17, 104.47.118.145, 104.47.118.177, UDP_-_EDNS0_4096_D_KN)
  • nist-gov.mail.protection.outlook.com/A: The response had an invalid RCODE (FORMERR) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (104.47.67.17, 104.47.68.17, 104.47.118.145, 104.47.118.177, UDP_-_EDNS0_4096_D_KN)
  • nist-gov.mail.protection.outlook.com/AAAA: The response had an invalid RCODE (FORMERR) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (104.47.67.17, 104.47.68.17, 104.47.118.145, 104.47.118.177, UDP_-_EDNS0_4096_D_KN)

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