Skip to content

Hostname

dukanexport.com

Last fetched

dukanexport.com resolves to 3.137.135.180, announced in 3.136.0.0/13 by AMAZON-02 - Amazon.com, Inc. in US. dukanexport.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 · dukanexport.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/dukanexport.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of dukanexport.com owner
Contact emails
0079f575-9d44-4a8d-a6a2-6ff87dd12e5a@identity-protect.org, 2067a945-0034-4571-a46c-8b1b6fdfe4dd@identity-protect.org, 4c469849-a09c-4600-a5b9-a224627bc6c7@identity-protect.org, 771bdcea-ed73-4a8a-b265-8ec3e874b879@identity-protect.org, 78d51d73-d7b8-44d7-ac97-ca65fd8e1d8a@identity-protect.org, ab91bf36-e6ef-41a0-b3c8-c8088d6bf5d8@identity-protect.org, owner-384563@dukanexport.com.whoisprivacyservice.org

Mail and authentication

Nameservers

  • ns-55.awsdns-06.com
  • ns-581.awsdns-08.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-1139.awsdns-14.org
  • ns-1728.awsdns-24.co.uk

Threat-feed evidence

History

Related pages

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