naver.jp
Observed Jul 18, 2026, 06:13 UTC (2d ago). Every field below was attested with an Ed25519 signature at scan time.
Not responding
Signed observation on record.
tranco_10k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat naver.jp actually stands on - every host below is a signed observation
naver.jp
NS
ns1.naver.jpans2.linecorp.comns2.naver.jpans1.linecorp.com
naver.jp + linecorp.comanswers its DNS
HTTPS probe
server_error
Server error (5xx) 530 Server Error
HTTP status530
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time227 ms
DNS resolutionNOERROR
Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".
DNS Records
TXT 1
v=spf1 include:naver.com include:spf.naver.jp ~all
NS 4
ns1.naver.jpans2.linecorp.comns2.naver.jpans1.linecorp.com
SOA 1
ns2.naver.jp domain.linecorp.com
TLS Certificates (0)
None.
Subdomains (4)
The proof
Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; nothing leaves your machine.
Verify this receiptPut the receipt on your own site. A live badge showing what DomainDrift observes and signs for naver.jp. It updates itself. It attests a signed observation - not that the site is safe.
<a href="https://domaindrift.io/t/naver.jp">
<img src="https://domaindrift.io/badge/naver.jp.svg"
width="300" height="64" alt="DomainDrift signed observations for naver.jp">
</a>
Ed25519 Receipt
- Receipt ID
bdbe7602-de68-4cb5-92ed-466eab48d3e7- Output Hash
4bc39b2d247f0af50e3354c2b6e13d7b679b8d11a7ea7d71602c10546917f34f- Signature
ed25519:1ac34eb2fa02c3753b99963fa39d89dfceafd9a9ffa8fe78ffbf14e941e376adf09f907a0402bafa6bf08dd61258795ce95120f3dc152d3122ce793a46942002- Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff- Parent
(genesis)- Plane
- fast