Hostname
spookyaction.co
Last fetched
spookyaction.co resolves to 15 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
spookyaction.co resolves to 15 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 16.12.89.235 | 16.12.88.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.83.227 | 3.5.83.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.86.218 | 3.5.86.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.87.14 | 3.5.87.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.218.180.146 | 52.218.180.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.148.43 | 52.92.144.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.179.171 | 52.92.176.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.190.75 | 52.92.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.193.99 | 52.92.192.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.194.235 | 52.92.192.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.205.147 | 52.92.200.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.205.243 | 52.92.200.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.210.115 | 52.92.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.213.19 | 52.92.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.213.83 | 52.92.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with spookyaction.co in WhisperGraph.
Subdomains
1 observed subdomain of spookyaction.co.
| Subdomain |
|---|
| www.spookyaction.co |
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for spookyaction.co.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | emailsrvr.com |
Related pages
Pivot deeper into the graph from spookyaction.co.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "spookyaction.co"})-[: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.