Domain

map.naver.com

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

DNS Check HTTP Check Run Full Scan .com TLD

Run a live full scan of map.naver.com

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now

Hosting IPs

A/AAAA targets

Subdomains

—

CT + scan + body

Record Types

seen in DNS

Observed Certs

—

in our scans

DNS Records

110.93.151.134, 110.93.151.164, 202.179.180.81, 202.179.180.91

AAAA

—

TXT

—

CNAME

—

CAA

—

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

34.160.221.17:443 href · ×23

15.164.111.93:443 href · ×14

101.79.19.243:80 href · ×13

139.150.80.127:443 href · ×11

141.164.39.30:80 href · ×10

101.79.21.32:443 href · ×10

3.34.226.187:443 href · ×8

180.210.79.202:80 href · ×5

106.253.235.37:443 href · ×4

211.199.109.210:443 href · ×4

13.209.210.157:443 href · ×3

43.203.172.192:80 href · ×3

58.229.178.110:443 href · ×3

220.95.232.164:443 href · ×3

220.95.232.164:80 href · ×3

1.234.75.77:443 href · ×3

64.176.227.240:443 href · ×3

121.156.134.200:443 href · ×2

3.38.80.81:443 href · ×2

222.235.212.50:443 href · ×2

13.124.5.5:443 href · ×2

211.214.155.214:80 href · ×2

219.248.240.129:443 href · ×2

54.180.20.238:443 href · ×2

3.34.52.138:443 href · ×2

1.234.65.24:443 href · ×2

43.201.20.80:80 href · ×2

3.39.24.97:443 href · ×2

180.69.51.83:443 href · ×2

49.50.134.113:443 href · ×2

158.179.160.187:80 href · ×2

221.142.226.63:80 href · ×2

15.164.54.81:80 href · ×2

13.209.118.157:443 href · ×2

119.17.142.183:80 href · ×2

175.119.224.151:443 href · ×2

43.202.197.4:80 href · ×2

64.176.232.191:443 href · ×2

124.221.229.238:443 href · ×2

43.200.23.231:443 href · ×2

172.235.202.125:443 href · ×2

49.50.136.198:443 href · ×2

49.247.13.73:80 href · ×1

218.150.101.161:443 href · ×1

34.22.93.254:443 href · ×1

43.200.54.43:80 href · ×1

116.124.5.58:80 href · ×1

13.125.34.129:80 href · ×1

14.41.77.238:8080 href · ×1

61.72.180.114:443 href · ×1

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type	Value	First seen	Last seen
A	110.93.151.134	2026-05-25 21:58:50.500	2026-07-28 19:48:54.308
A	202.179.180.91	2026-05-25 21:58:50.500	2026-07-28 19:48:54.308
A	110.93.151.164	2026-05-25 21:58:50.500	2026-07-28 19:48:54.308
A	202.179.180.81	2026-05-25 21:58:50.500	2026-07-28 19:48:54.308