Hostname
precursor.ai
Last fetched
precursor.ai resolves to 16 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
precursor.ai resolves to 16 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 3.5.77.217 | 3.5.77.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.77.33 | 3.5.77.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.77.77 | 3.5.77.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.78.40 | 3.5.78.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.81.241 | 3.5.81.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.83.127 | 3.5.83.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.218.182.154 | 52.218.182.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.218.233.82 | 52.218.233.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.218.236.66 | 52.218.236.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.181.139 | 52.92.176.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.186.147 | 52.92.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.190.51 | 52.92.184.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.235.43 | 52.92.232.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.240.43 | 52.92.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.242.91 | 52.92.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.248.163 | 52.92.248.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with precursor.ai in WhisperGraph.
Subdomains
2 observed subdomains of precursor.ai.
| Subdomain |
|---|
| _spfm.precursor.ai |
| www.precursor.ai |
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for precursor.ai.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | dc-aa8e722993._spfm.precursor.ai |
Related pages
Pivot deeper into the graph from precursor.ai.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "precursor.ai"})-[: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.