Hostname
stenhouse.com
Last fetched
stenhouse.com resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:2 as the registrar.
Nutrition Label
Resolution chain
stenhouse.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.18.36.220 | 104.18.36.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.64.151.36 | 172.64.151.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:2
- Organization
- highlights for children,
- Contact emails
Subdomains
31 observed subdomains of stenhouse.com.
Showing 25 of 31. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from stenhouse.com in the public web crawl.
451 sites link to this hostname.
1 site linked to from this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
SPF policy
12 SPF mechanisms authorising senders for stenhouse.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 5618249.spf02.hubspotemail.net |
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | et._spf.pardot.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | spf.workfront.com |
| SPF_IP | 207.166.101.207/32 |
| SPF_IP | 207.166.92.11/32 |
| SPF_IP | 207.166.95.11/32 |
| SPF_IP | 209.170.246.101/24 |
| SPF_IP | 66.192.198.48/28 |
Related pages
Pivot deeper into the graph from stenhouse.com.
- IP · 104.18.36.220
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:2
- Country · CA
- Email · dnsadmin@highlights-corp.com
- TLD · .com
- Browse hostnames · st…
- 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: "stenhouse.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.