HOW.IS
?

How is naver.com?

Looks fine risk 0/100

Registered 29 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 1448 ms.

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

How naver.com looks right now
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
Site
200
1448 ms · ends at www.naver.com
HTTPS
36 d
left on a Let's Encrypt certificate
Age
29 years
registered 1997-09-12
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records4 record types
A223.130.192.247
223.130.200.236
223.130.200.219
223.130.192.248
MX20 mx6.mail.naver.com
10 mx1.mail.naver.com
20 mx4.mail.naver.com
20 mx5.mail.naver.com
NSns2.naver.com
ns3.naver.com
ns1.naver.com
TXTgoogle-site-verification=B_dAfnJNNK2GwYDLRl2bdAGtfiyqMjEddjUeDI1Z6sk
google-site-verification=fK9dDFcEOeNM2Wr3xzNAN-XLcerfAGpOABdSYiqw4_s
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
facebook-domain-verification=0qyhf0qnkiuqfx4owhfuvwvsvjz8fk
_3cnydf6cxi66oarl6yhoij3qzp72cwe
autodesk-domain-verification=PNb3nwmN_N_vGtZjI0kq
yahoo-verification-key=c5FwvFg2sxJ9LbDw0prZbUryrfkGgC80tKLUTsLgHD8=
RegistrationGabia, Inc.
registrarGabia, Inc.
registered1997-09-12
expires2032-09-11
last changed2025-10-22
nameserversns1.naver.com
ns2.naver.com
ns3.naver.com
statusclient delete prohibited
client transfer prohibited
client update prohibited
registered 1997-09-12expires 2032-09-11
HTTPS certificate36 days left
validyes
issuerLet's Encrypt
coversnaver.asia, naver.co, naver.co.kr, naver.com, naver.kr, naver.net, new.www.naver.com, next.www.naver.com, www.naver.asia, www.naver.co, www.naver.co.kr, www.naver.kr
protocolTLSv1.3
issued 2026-09-03expires 2026-12-02
DNSSECinsecure

Domain is not signed with DNSSEC

. → com → naver.com
Email authenticationfair
SPFpass 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
DMARCwarning policy none
DKIMnone of 1 common selectors

Whether mail claiming to be from this domain can be checked as genuine.

Security scoregrade C · 143/205
Basic Security
10/40missing: DNSSEC Enabled, Nameserver Diversity
Record Security
23/45missing: CAA Records, DMARC Record, DKIM Presence
Advanced Security
15/25missing: SOA Record Configuration, IPv6 Support
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 14 lookups
SURBL MultidomainURIBL MultidomainSpamCop223.130.192.248Barracuda223.130.192.248UCEPROTECT Level 1223.130.192.248SpamCop223.130.192.247Barracuda223.130.192.247UCEPROTECT Level 1223.130.192.247SpamCop223.130.200.236Barracuda223.130.200.236UCEPROTECT Level 1223.130.200.236SpamCop223.130.200.219Barracuda223.130.200.219UCEPROTECT Level 1223.130.200.219

Green: clean. Red: listed. Grey: the list did not answer.

Ask it yourself

Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.

curl "https://how.is/v1/domain/trust?domain=naver.com" \ -H "Authorization: Bearer $HOWIS_KEY" # or pay per call in USDC (x402), no key: the 402 tells your agent the price curl -i "https://how.is/v1/domain/profile?domain=naver.com"

MCP: add https://how.is/mcp to Claude, Codex or Cursor (one-line install) and ask for domain_trust on naver.com. Reference: /llms.txt.

Watch naver.com. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.

Watch — $1 / 30 days