Hostname
squidproxies.com
Last fetched
squidproxies.com resolves to 104.21.17.176, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. squidproxies.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.21.17.176
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.177.188
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:2487
- Registrant organisation
- matt wilson
- Contact emails
- grtkgmsttb@whoisprivacyprotect.com, service@squidproxies.com, wcdlslwhdd@whoisprivacyprotect.com, 4d4ce789cf026a3729c26748a09b8ffc.gdrp@customers.whoisprivacycorp.com, info@domain-contact.org
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- alla.ns.cloudflare.com
- dean.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
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
- mail.squidproxies.com
SPF policy
- include: amazonses.com
- include: _spf.createsend.com
- include: _spf.google.com
- include: spf.mandrillapp.com
- a: squidproxies.com
- mx: squidproxies.com
- include: spf.mtasv.net
- ip: 104.225.132.126
- ip: 173.255.249.43
- ip: 64.64.30.198
- ip: 64.64.31.52
Threat-feed evidence
History
Related pages
Pivot from squidproxies.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: "squidproxies.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.