samsung.com
Updated:
2024-08-27 14:55:06 UTC (8 months ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (9)
- samsung.com/A
- samsung.com/MX
- samsung.com/NS
- samsung.com/SOA
- samsung.com/SOA
- samsung.com/SOA
- samsung.com/SOA
- samsung.com/SOA
- samsung.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of samsung.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 59354)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to samsung.com
Secure (1)
- . to com
Notices
Errors (4)
- samsung.com zone: The following NS name(s) did not resolve to address(es): auth01.nhn.ic, auth02.nhn.ic, auth03.nhn.ic, auth04.nhn.ic, auth01.sam.ic, auth02.sam.ic, auth03.sam.ic, auth04.sam.ic
- samsung.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (203.241.135.186, 2001:330:a:b:112:106:53:58, 2001:330:a:300b:112:107:53:58)
- samsung.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (203.241.135.186, 2001:330:a:b:112:106:53:58, 2001:330:a:300b:112:107:53:58, UDP_-_NOEDNS_)
- samsung.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (203.241.135.186, 2001:330:a:b:112:106:53:58, 2001:330:a:300b:112:107:53:58, UDP_-_NOEDNS_)
Warnings (10)
- ./DNSKEY (alg 8, id 20038): 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 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: 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_512_D_KN)
- com to samsung.com: Authoritative AAAA records exist for dnssm.samsung.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to samsung.com: Authoritative AAAA records exist for dnssm2.samsung.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to samsung.com: Authoritative AAAA records exist for dnsst.samsung.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to samsung.com: Authoritative AAAA records exist for dnsst2.samsung.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to samsung.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): auth04.sam.ic, dns-gi2.samsung.com, auth03.sam.ic, auth01.sam.ic, auth02.nhn.ic, auth04.nhn.ic, auth01.nhn.ic, auth02.sam.ic, auth03.nhn.ic See RFC 1034, Sec. 4.2.2.
- com/DS (alg 13, id 19718): 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/DS (alg 13, id 19718): 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)
JavaScript is required to make the graph below interactive.
