Skip to content

Hostname

therma.com

Last fetched

therma.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. therma.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 · therma.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/therma.com

Resolution chain

No IPv4 resolution is recorded for therma.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:291
Registrant organisation
jewella privacy - 0e263
Contact emails
therma.com@directnicwhoiscompliance.com, therma.com@dnic.jewellaprivacy.com, jparisi@therma.com

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

  • ns1-08.azure-dns.com
  • ns4-08.azure-dns.info
  • ns2-08.azure-dns.net
  • ns3-08.azure-dns.org

MX records

  • therma-com.mail.protection.outlook.com

SPF policy

  • include: spf.constantcontact.com
  • include: _spf.dayforcehcm.com
  • include: spf.protection.outlook.com
  • a: therma.com
  • ip: 100.43.243.186
  • ip: 108.74.1.180
  • ip: 108.74.1.181
  • ip: 12.139.38.98
  • ip: 129.210.242.9
  • ip: 166.253.16.196
  • ip: 192.169.21.78
  • ip: 208.74.176.106
  • ip: 24.104.112.100
  • ip: 24.104.112.70
  • ip: 50.253.87.17
  • ip: 63.42.228.93
  • ip: 64.71.23.30
  • ip: 64.71.25.154
  • ip: 64.71.25.174
  • ip: 64.71.3.2
  • ip: 64.79.121.142
  • ip: 64.79.125.250
  • ip: 67.148.203.142
  • ip: 67.207.120.134
  • ip: 67.207.121.94
  • ip: 68.65.224.198
  • ip: 76.77.189.34

Threat-feed evidence

History

Related pages

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