Hostname
surgeons.org
Last fetched
surgeons.org resolves to 4 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:48 as the registrar.
Nutrition Label
Resolution chain
surgeons.org resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.20.28.79 | 104.20.16.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.66.145.154 | 172.66.144.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 8.47.69.0 | 8.47.69.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | US |
| 8.6.112.0 | 8.6.112.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | US |
WHOIS identity
- Registrar
- iana:48
- Organization
- robby castillo
- Contact emails
Subdomains
63 observed subdomains of surgeons.org.
Showing 25 of 63. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from surgeons.org in the public web crawl.
1,100 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
12 SPF mechanisms authorising senders for surgeons.org.
| Mechanism | Target |
|---|---|
| SPF_A | surgeons.org |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | customer.mailguard.com.au |
| SPF_INCLUDE | eventsairmail.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | servers.mcsv.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 125.7.117.103 |
| SPF_IP | 13.70.186.239 |
| SPF_IP | 203.122.217.235 |
| SPF_IP | 52.64.219.175 |
| SPF_IP | 52.65.238.77/32 |
Related pages
Pivot deeper into the graph from surgeons.org.
- IP · 104.20.28.79
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:48
- Country · CA
- Email · robby.castillo@surgeons.org
- TLD · .org
- Browse hostnames · su…
- 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: "surgeons.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.