Hostname
tennfire.com
Last fetched
tennfire.com resolves to 1 IPv4 address operated by GOOGLE-CLOUD-PLATFORM - Google LLC in US. WHOIS lists iana:636 as the registrar.
Nutrition Label
Resolution chain
tennfire.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.198.107.121 | 104.198.96.0/20 | AS396982 | GOOGLE-CLOUD-PLATFORM - Google LLC | US |
WHOIS identity
- Registrar
- iana:636
- Organization
- jonathan denham
- Contact emails
- 13wn9nuonmmiy4bn@private-contact.com
- 1e15zqqj62p0ezuc@private-contact.com
- fglpgtmjlazvth0z@private-contact.com
- hkpuaqhu20lobogl@private-contact.com
- pbkblnwinc6o2ua2@private-contact.com
- pijr0o1grimoihp6@private-contact.com
- rstlskx9mwwnop0z@private-contact.com
- tlimehjljubkfuqn@private-contact.com
- vhi4gu0ipembl39f@private-contact.com
- wfrpober0mv2oxmo@private-contact.com
- yqsxumboio2rwjnx@private-contact.com
Subdomains
2 observed subdomains of tennfire.com.
| Subdomain |
|---|
| remote.tennfire.com |
| www.tennfire.com |
Web-graph footprint
Distinct hostnames that link to or from tennfire.com in the public web crawl.
5 sites link to this hostname.
34 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
2 SPF mechanisms authorising senders for tennfire.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf-us.emailsignatures365.com |
| SPF_INCLUDE | spf.protection.outlook.com |
Related pages
Pivot deeper into the graph from tennfire.com.
- IP · 104.198.107.121
- ASN · AS396982GOOGLE-CLOUD-PLATFORM - Google LLC
- Registrar · iana:636
- Country · US
- Email · 13wn9nuonmmiy4bn@private-contact.com
- TLD · .com
- Browse hostnames · te…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "tennfire.com"})-[: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.