Skip to content

Hostname

cdm.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

amazon com

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
camp dresser & mckee
Contact emails
domains@cdmsmith.com, gerthjg@cdm.com, q36n759j6c3@networksolutionsprivateregistration.com

Subdomains

Subdomain
crbweb01.cdm.com
crbweb02.cdm.com
ftp.cdm.com
gis.cdm.com
gis1.cdm.com
gis2.cdm.com
go.cdm.com
hosts235.cdm.com
hosts241.cdm.com
projectwise.cdm.com
secureguest.cdm.com
www.cdm.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

  • ns53.worldnic.com
  • ns54.worldnic.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

  • cdm-com.mail.protection.outlook.com

SPF policy

  • include: authsmtp.com
  • ip: 98.124.160.253

Threat-feed evidence

History

Related pages

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