Hostname
reasons.org
Last fetched
reasons.org resolves to 6 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
reasons.org resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.21.68.209 | 104.21.64.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.198.121 | 172.67.192.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.96.11 | 188.114.96.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.96.3 | 188.114.96.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.97.11 | 188.114.97.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.97.3 | 188.114.97.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:146
- Organization
- craig kletzien
- Contact emails
Subdomains
22 observed subdomains of reasons.org.
Showing 20 of 22. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from reasons.org in the public web crawl.
1,003 sites link to this hostname.
922 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
6 SPF mechanisms authorising senders for reasons.org.
| Mechanism | Target |
|---|---|
| SPF_A | reasons.org |
| SPF_INCLUDE | emailsrv.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 208.70.208.0/22 |
| SPF_IP | 69.84.129.224/27 |
| SPF_MX | reasons.org |
Related pages
Pivot deeper into the graph from reasons.org.
- IP · 104.21.68.209
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:146
- Country · CA
- Email · ckletzien@reasons.org
- TLD · .org
- Browse hostnames · re…
- 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: "reasons.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.