Skip to content

Hostname

thecodingmachine.com

Last fetched

thecodingmachine.com resolves to 51.178.138.109, announced in 51.178.0.0/16 by OVH - OVH SAS in FR. thecodingmachine.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 · thecodingmachine.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/thecodingmachine.com

Resolution chain

IPv6 resolution

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

Attribution

ovh

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
gdpr-masking@gdpr-masked.com, d.negrier@thecodingmachine.com, 1589cf5a-89bd-4613-b523-1434a00190dc@identity-protect.org, 787e13aa-d56e-4a18-8df0-e425a4e573a8@identity-protect.org, 7c14bab0-0652-4cd2-8665-e92ea2c302c6@identity-protect.org, 9867b978-6b31-49e4-a262-6f6812b3d585@identity-protect.org, aa83eece-eec4-47e1-9e1d-61bed9d4b8ac@identity-protect.org, contact@privacyprotect.org, fe7b5d3f-c82a-4b2c-a5d0-f6dfc24b8bc2@identity-protect.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-140.awsdns-17.com
  • ns-643.awsdns-16.net
  • ns-1441.awsdns-52.org
  • ns-1669.awsdns-16.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: spf.mailjet.com
  • include: spf.sendinblue.com
  • mx: thecodingmachine.com
  • include: one.zoho.eu
  • ip: 141.94.162.152
  • ip: 51.79.29.147

Threat-feed evidence

History

Related pages

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