Skip to content

Hostname

cartdna.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
033c9af9d26441ba9509723cf7175601.protect@withheldforprivacy.com, 030fdb9237f2a044badb84a611f173880a4bad34@private.design

Subdomains

Subdomain
admin.cartdna.com
app.cartdna.com
in.cartdna.com
logs.cartdna.com
merchants.cartdna.com
mobileapi.cartdna.com
pay.cartdna.com
sub-api.cartdna.com
testapp.cartdna.com
webmail.cartdna.com
wp.cartdna.com
www.cartdna.com

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

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
  • 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

MX records

  • cartdna-com.mail.protection.outlook.com
  • ms56578210.msv1.invalid

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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