Hostname
thefire.org
Last fetched
thefire.org resolves to 5 IPv4 addresses operated by FASTLY - Fastly, Inc. in US. WHOIS lists iana:1068 as the registrar.
Nutrition Label
Resolution chain
thefire.org resolves to 5 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 146.75.94.132 | 146.75.92.0/22 | AS54113 | FASTLY - Fastly, Inc. | US |
| 151.101.74.132 | 151.101.72.0/22 | AS54113 | FASTLY - Fastly, Inc. | US |
| 34.73.189.215 | 34.73.176.0/20 | AS396982 | GOOGLE-CLOUD-PLATFORM - Google LLC | US |
| 34.74.8.155 | 34.74.0.0/20 | AS396982 | GOOGLE-CLOUD-PLATFORM - Google LLC | US |
| 34.75.104.115 | 34.75.96.0/20 | AS396982 | GOOGLE-CLOUD-PLATFORM - Google LLC | US |
WHOIS identity
- Registrar
- iana:1068
- Organization
- - -
- Contact emails
Subdomains
24 observed subdomains of thefire.org.
Showing 22 of 24. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from thefire.org in the public web crawl.
4,649 sites link to this hostname.
5,034 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
22 SPF mechanisms authorising senders for thefire.org.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | _spf.qualtrics.com |
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | email.prnewswire.com |
| SPF_IP | 103.151.192.0/23 |
| SPF_IP | 13.111.0.0/16 |
| SPF_IP | 168.245.40.179/32 |
| SPF_IP | 185.12.80.0/22 |
| SPF_IP | 188.172.128.0/20 |
| SPF_IP | 192.161.144.0/20 |
| SPF_IP | 192.254.123.144/32 |
| SPF_IP | 192.254.126.246/32 |
| SPF_IP | 198.21.6.113/32 |
| SPF_IP | 208.117.50.171/32 |
| SPF_IP | 216.198.0.0/18 |
| SPF_IP | 38.140.17.210 |
| SPF_IP | 38.140.202.234 |
| SPF_IP | 50.31.44.75/32 |
| SPF_IP | 68.238.233.130 |
| SPF_IP | 69.72.47.212/32 |
| SPF_IP | 96.231.174.115 |
| SPF_MX | thefire.org |
Related pages
Pivot deeper into the graph from thefire.org.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "thefire.org"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.