Skip to content

Hostname

moy.kr

Last fetched

moy.kr resolves to 183.111.141.14, announced in 183.104.0.0/13 by KIXS-AS-KR-KR - Korea Telecom in KR. moy.kr is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Mon, 14 Sep 2026 19:54:16 GMT

Nutrition Label

WHISPER CANON · moy.krRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency3.3/10Resolver footprint9.2/10canon.whisper.security/host/moy.kr

Resolution chain

IPv6 resolution

No AAAA record for moy.kr is recorded in WhisperGraph.

Attribution

korea

ORIGIN_AS

WHOIS identity

Registrar
registrar:(?)????????
Registrant organisation
???

Subdomains

Subdomain
postmaster.moy.kr
www.moy.kr

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

Sample outbound links

Mail and authentication

Nameservers

  • ns.cafe24.com
  • ns0.cafe24.com
  • ns1.cafe24.com
  • ns2.cafe24.com
  • b.dns.kr
  • c.dns.kr
  • d.dns.kr
  • e.dns.kr
  • f.dns.kr
  • g.dns.kr
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • mw-002.cafe24.com

SPF policy

  • ip: 183.111.141.14

Threat-feed evidence

History

Related pages

Pivot from moy.kr 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: "moy.kr"})-[: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.