Skip to content

Hostname

me2day.com

Last fetched

me2day.com resolves to 202.131.25.24, announced in 202.131.24.0/22 by nhn-AS-KR-KR - NAVER Cloud Corp. in KR. me2day.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · me2day.comRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/me2day.com

Resolution chain

IPv6 resolution

No AAAA record for me2day.com is recorded in WhisperGraph.

Attribution

naver

ORIGIN_AS

WHOIS identity

Registrar
iana:244
Registrant organisation
naver
Contact emails
white.4818@navercorp.com

Subdomains

Subdomain
static1.me2day.com
static2.me2day.com

Showing 2 of 2 subdomains (2 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • ns1.naver.com
  • ns2.naver.com

Threat-feed evidence

History

Related pages

Pivot from me2day.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "me2day.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.