Skip to content

Hostname

danble.co.kr

Last fetched

danble.co.kr resolves to 13.227.192.112, announced in 13.227.213.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. danble.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 · danble.co.krRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.5/10canon.whisper.security/host/danble.co.kr

Resolution chain

IPv6 resolution

No AAAA record for danble.co.kr is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

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

Subdomains

Subdomain
admin.danble.co.kr
alpha-admin.danble.co.kr
alpha-api.danble.co.kr
alpha-vercel.danble.co.kr
app-alpha.danble.co.kr
beta-vercel.danble.co.kr
dashboard.danble.co.kr
management-alpha.danble.co.kr
managementofficial.danble.co.kr
storybook.danble.co.kr

Showing 10 of 10 subdomains (10 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-273.awsdns-34.com
  • ns1.vercel-dns.com
  • ns-705.awsdns-24.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
  • ns-1404.awsdns-47.org
  • ns-1829.awsdns-36.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

Threat-feed evidence

History

Related pages

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