Skip to content

Hostname

next-engine.co.kr

Last fetched

next-engine.co.kr resolves to 13.226.155.114, announced in 13.226.152.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. next-engine.co.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 · next-engine.co.krRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/next-engine.co.kr

Resolution chain

IPv6 resolution

No AAAA record for next-engine.co.kr is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for next-engine.co.kr. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
admin.next-engine.co.kr
app.next-engine.co.kr
devmonitor.next-engine.co.kr
devweb.next-engine.co.kr
help.next-engine.co.kr
manual.next-engine.co.kr
www.next-engine.co.kr

Showing 7 of 7 subdomains (7 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-113.awsdns-14.com
  • ns-562.awsdns-06.net
  • ns-1213.awsdns-23.org
  • ns-1811.awsdns-34.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

Pivot from next-engine.co.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: "next-engine.co.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.