Hostname
whyequis.com
Last fetched
whyequis.com resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:1068 as the registrar.
Nutrition Label
Resolution chain
whyequis.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.21.74.219 | 104.21.64.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.163.108 | 172.67.160.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:1068
- Organization
- on behalf of whyequis.com owner
- Contact emails
- dataprotected@maskeddetails.com
- 89ac2ee149384d7884af634c6acd521d.protect@withheldforprivacy.com
- 1f112789-b871-4d4d-bc32-3cb8a54e5b08@identity-protect.org
- 8d114188-afbd-405a-89c1-2b60d0e49498@identity-protect.org
- c27bc6f1-4bfa-4e46-821c-4239de5550ea@identity-protect.org
- f63062e9-33cc-479c-96a8-0bb574f7c1f9@identity-protect.org
- owner-6966457@whyequis.com.whoisprivacyservice.org
Subdomains
1 observed subdomain of whyequis.com.
| Subdomain |
|---|
| www.whyequis.com |
Web-graph footprint
Distinct hostnames that link to or from whyequis.com in the public web crawl.
9 sites link to this hostname.
1 site linked to from this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
SPF policy
4 SPF mechanisms authorising senders for whyequis.com.
| Mechanism | Target |
|---|---|
| SPF_A | whyequis.com |
| SPF_INCLUDE | spf.web-hosting.com |
| SPF_IP | 198.54.125.232 |
| SPF_MX | whyequis.com |
Related pages
Pivot deeper into the graph from whyequis.com.
- IP · 104.21.74.219
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:1068
- Country · CA
- Email · dataprotected@maskeddetails.com
- TLD · .com
- Browse hostnames · wh…
- 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: "whyequis.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.