Skip to content

Hostname

heungaline.com

Last fetched

heungaline.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. heungaline.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 · heungaline.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/heungaline.com

Resolution chain

No IPv4 resolution is recorded for heungaline.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:244
Contact emails
isteam@sinokor.co.kr

Subdomains

Subdomain
ebiz.heungaline.com
ebizprt.heungaline.com
repair.heungaline.com
tasks.heungaline.com
www.heungaline.com

Showing 5 of 5 subdomains (5 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

  • ns1-09.azure-dns.com
  • ns4-09.azure-dns.info
  • ns2-09.azure-dns.net
  • 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
  • ns3-09.azure-dns.org

MX records

  • heungaline-com.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: spf.protection.outlook.com
  • ip: 211.104.10.12
  • ip: 211.104.10.15
  • ip: 211.104.10.25
  • ip: 211.104.10.79
  • ip: 211.104.10.80
  • ip: 211.104.10.81

Threat-feed evidence

History

Related pages

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