tv.naver.com

Zone naver.com · Checked 22 October 2026, 11:13 UTC · via 8.8.8.8
!Passed with warnings
24 passed 3 warnings 0 failed 4 info

Registration

info

.com generic · Gabia, Inc. · expires 2032-09-11

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Gabia, Inc.
Registered
12 September 1997
Last changed
22 October 2025
Expires
11 September 2032
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns1.naver.com, ns2.naver.com, ns3.naver.com
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2032-09-11 #3
    The registration is valid until 2032-09-11 (2150 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.naver.com, ns2.naver.com, ns3.naver.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.naver.com, ns2.naver.com, ns3.naver.com
NS in the zone
ns1.naver.com, ns2.naver.com, ns3.naver.com
NameserverAddressesNetwork (AS)Glue
ns1.naver.com61.247.220.6AS23576 nhn-AS-KR-KR - NAVER Cloud Corp., KR61.247.220.6
ns2.naver.com61.247.221.6AS23576 nhn-AS-KR-KR - NAVER Cloud Corp., KR61.247.221.6
ns3.naver.com211.188.44.6AS23576 nhn-AS-KR-KR - NAVER Cloud Corp., KR211.188.44.6

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.naver.com, ns2.naver.com, ns3.naver.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.naver.com, ns2.naver.com, ns3.naver.com.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 3 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS23576 (nhn-AS-KR-KR - NAVER Cloud Corp., KR): 3 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.naver.com 61.247.220.6NOERROR, 247 ms, authoritativenoyes / yesrefused-
ns2.naver.com 61.247.221.6NOERROR, 102 ms, authoritativenoyes / yesrefused-
ns3.naver.com 211.188.44.6NOERROR, 5 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026102205 · primary ns1.naver.com

Found

Primary (MNAME)
ns1.naver.com
Contact (RNAME)
webmaster.naver.com
Serial
2026102205
Refresh / retry
21600 s / 1800 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns1.naver.com (61.247.220.6)2026102205
ns2.naver.com (61.247.221.6)2026102205
ns3.naver.com (211.188.44.6)2026102205

Checks

  • ✓ Serial 2026102205 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 6h, retry 30m, expire 14d, negative TTL 3m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.naver.com is one of the listed nameservers.
  • ✓ Contact webmaster@naver.com #25
    The SOA RNAME webmaster.naver.com means webmaster@naver.com.
  • ✓ Date-based serial #26
    The serial 2026102205 follows the YYYYMMDDnn convention (2026-10-22).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

19 records at the apex

Found

Read from
61.247.220.6:53
TypeValueTTL
SOAns1.naver.com. webmaster.naver.com. 2026102205 21600 1800 1209600 180300
NSns2.naver.com.86400
NSns1.naver.com.86400
NSns3.naver.com.86400
A223.130.200.219300
A223.130.200.236300
A223.130.192.247300
A223.130.192.248300
MX10 mx1.mail.naver.com.300
MX20 mx6.mail.naver.com.300
MX20 mx5.mail.naver.com.300
MX20 mx4.mail.naver.com.300
TXT"autodesk-domain-verification=PNb3nwmN_N_vGtZjI0kq"300
TXT"google-site-verification=fK9dDFcEOeNM2Wr3xzNAN-XLcerfAGpOABdSYiqw4_s"300
TXT"v=spf1 ip4:111.91.135.0/27 ip4:125.209.208.0/20 ip4:125.209.224.0/19 ip4:210.89.163.112 ip4:210.89.173.104/29 ip4:114.111.35.0/24 ip4:61.247.196.0/24 ip4:61.247.197.0/24 ~all"300
TXT"_3cnydf6cxi66oarl6yhoij3qzp72cwe"300
TXT"yahoo-verification-key=c5FwvFg2sxJ9LbDw0prZbUryrfkGgC80tKLUTsLgHD8="300
TXT"google-site-verification=B_dAfnJNNK2GwYDLRl2bdAGtfiyqMjEddjUeDI1Z6sk"300
TXT"facebook-domain-verification=0qyhf0qnkiuqfx4owhfuvwvsvjz8fk"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35