Skip to content

Hostname

thermea.com

Last fetched

thermea.com resolves to 13.216.86.34, announced in 13.216.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. thermea.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 · thermea.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/thermea.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of thermea.com owner
Contact emails
907863@privacy-link.com, 0f82281b-a49a-4b73-b563-d37750ee42fb@identity-protect.org, 4ea65bce-4cb2-45e0-8dcb-23df993c8ad6@identity-protect.org, 5bc5028a-82cd-4760-b66b-8eed5b1120c5@identity-protect.org, 71bf7fce-5587-4075-ac3b-b97480cf6713@identity-protect.org, 8069a6ee-e89f-4a4c-afea-72b66ad61574@identity-protect.org, b40b2815-6e61-4a04-9ba9-a11b9a9ad871@identity-protect.org, bfceb947-5fe3-4d7f-a9cf-95d7a4a78043@identity-protect.org, owner-5211597@thermea.com.whoisprivacyservice.org, owner-9618757@thermea.com.whoisprivacyservice.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-355.awsdns-44.com
  • ns-743.awsdns-28.net
  • ns-1526.awsdns-62.org
  • ns-1561.awsdns-03.co.uk

MX records

  • thermea-com.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: spfa.cpmails.com
  • include: spf.emailsignatures365.com
  • include: cust-spf.exacttarget.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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