Hostname
thehypothesis.com
Last fetched
thehypothesis.com resolves to 104.20.45.41, announced in 104.20.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. thehypothesis.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.20.45.41
104.20.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.45.146
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.157.219
172.66.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.215.126
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:48
- Registrant organisation
- buydomains_com
- Contact emails
- brokerage@buydomains.com
Subdomains
| Subdomain |
|---|
| link.thehypothesis.com |
| prod-sfcc.thehypothesis.com |
| try.thehypothesis.com |
| www.thehypothesis.com |
Showing 4 of 4 subdomains (4 per page).
Mail and authentication
Nameservers
- elaine.ns.cloudflare.com
- kip.ns.cloudflare.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- us-smtp-inbound-1.mimecast.com
- us-smtp-inbound-2.mimecast.com
SPF policy
- ip: 64.135.78.20/32
- ip: 64.135.46.59/32
- ip: 64.135.46.60/32
- include: esp1.co
- include: us._netblocks.mimecast.com
- include: spf.protection.outlook.com
- a: hmail.uniformadvantage.com
Threat-feed evidence
History
Related pages
Pivot from thehypothesis.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: "thehypothesis.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.