Skip to content

Hostname

leocom.kr

Last fetched

leocom.kr resolves to 211.218.126.248, announced in 211.216.0.0/13 by KIXS-AS-KR-KR - Korea Telecom in KR. leocom.kr 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 · leocom.krRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.6/10canon.whisper.security/host/leocom.kr

Resolution chain

IPv6 resolution

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

Attribution

korea

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

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

Subdomains

Web-graph footprint

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

Mail and authentication

Nameservers

  • ns1.koreaidc.com
  • ns2.koreaidc.com
  • ns3.koreaidc.com
  • dns1.leocom.kr

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com
  • leocom.kr
  • leocom-kr.mail.protection.outlook.com

SPF policy

  • include: gmail.com

Threat-feed evidence

History

Related pages

Pivot from leocom.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: "leocom.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.