Hostname
spideraf.com
Last fetched
spideraf.com resolves to 19 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in JP. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
spideraf.com resolves to 19 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of spideraf.com owner
- Contact emails
- hostmaster@phybbit.com
- 53f9a6ee-c20f-4759-9801-36c7a46f5d33@identity-protect.org
- 5e6a616d-2aec-4b34-bceb-e3a1e9fb1c28@identity-protect.org
- 7e4f858a-5785-4c7f-83af-92c75e5d289d@identity-protect.org
- 7e67b11d-be0f-4949-af19-28b2c56caceb@identity-protect.org
- c4062dd8-906f-42e8-9bed-b30ac6e833f2@identity-protect.org
- c4e95b31-e00e-43e2-8df3-4e6377fa6ae5@identity-protect.org
- owner-2711483@spideraf.com.whoisprivacyservice.org
- owner-3541649@spideraf.com.whoisprivacyservice.org
- owner-7481478@spideraf.com.whoisprivacyservice.org
Subdomains
29 observed subdomains of spideraf.com.
Showing 25 of 29. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from spideraf.com in the public web crawl.
644 sites link to this hostname.
200 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
5 SPF mechanisms authorising senders for spideraf.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 19818430.spf06.hubspotemail.net |
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | sender.zohosubscriptions.com |
| SPF_INCLUDE | servers.mcsv.net |
Related pages
Pivot deeper into the graph from spideraf.com.
- IP · 13.158.127.88
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · JP
- Email · hostmaster@phybbit.com
- TLD · .com
- Browse hostnames · sp…
- 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: "spideraf.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.