jnj.com
Updated:
2024-10-24 18:45:00 UTC (27 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- jnj.com/A
- jnj.com/MX
- jnj.com/NS
- jnj.com/SOA
- jnj.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of jnj.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 29942)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to jnj.com
Secure (1)
- . to com
Notices
Warnings (6)
- ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 61050): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- com to jnj.com: Authoritative AAAA records exist for ns01.jnjdns.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to jnj.com: Authoritative AAAA records exist for ns02.jnjdns.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to jnj.com: Authoritative AAAA records exist for ns03.jnjdns.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to jnj.com: Authoritative AAAA records exist for ns04.jnjdns.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
