Hostname
affect3d.com
Last fetched
affect3d.com resolves to 3 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:1068 as the registrar.
Nutrition Label
Resolution chain
affect3d.com resolves to 3 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.26.12.202 | 104.26.0.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 104.26.13.202 | 104.26.0.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.74.246 | 172.67.64.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:1068
- Organization
- privacy service provided by withheld for privacy ehf
- Contact emails
Subdomains
7 observed subdomains of affect3d.com.
Web-graph footprint
Distinct hostnames that link to or from affect3d.com in the public web crawl.
Threat posture
History
Mail and authentication
SPF policy
17 SPF mechanisms authorising senders for affect3d.com.
| Mechanism | Target |
|---|---|
| SPF_A | affect3d.com |
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | _spf.natsfornetworks.com |
| SPF_INCLUDE | _spf.offerit.com |
| SPF_INCLUDE | ab.sendgrid.net |
| SPF_INCLUDE | mailgun.org |
| SPF_IP | 149.72.0.0/16 |
| SPF_IP | 159.183.0.0/16 |
| SPF_IP | 167.89.0.0/17 |
| SPF_IP | 168.245.0.0/17 |
| SPF_IP | 192.163.246.115 |
| SPF_IP | 192.254.112.0/20 |
| SPF_IP | 198.21.0.0/21 |
| SPF_IP | 198.37.144.0/20 |
| SPF_IP | 208.117.48.0/20 |
| SPF_IP | 50.31.32.0/19 |
| SPF_MX | affect3d.com |
Related pages
Pivot deeper into the graph from affect3d.com.
- IP · 104.26.12.202
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:1068
- Country · CA
- Email · 110136da23974f48b4cf2bd04c9317b9.protect@whoisguard.com
- TLD · .com
- Browse hostnames · af…
- 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: "affect3d.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.