samsung.com

Updated: 2024-09-14 11:12:44 UTC (7 months ago) Update now

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./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)

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_)

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.