Hostname
am.lilly.com
Last fetched
am.lilly.com resolves to 13 IPv4 addresses operated by LILLY-AS - Eli Lilly and Company in US.
Nutrition Label
Resolution chain
am.lilly.com resolves to 13 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 40.1.228.166 | 40.1.0.0/16 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.1.228.181 | 40.1.0.0/16 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.1.228.182 | 40.1.0.0/16 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.1.228.183 | 40.1.0.0/16 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.10.165.243 | 40.10.0.0/15 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.144.140.115 | 40.144.0.0/16 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.147.130.165 | 40.147.128.0/17 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.200.73.132 | 40.200.73.0/24 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.228.19.175 | 40.228.0.0/18 | AS4249 | LILLY-AS - Eli Lilly and Company | GB |
| 40.228.19.176 | 40.228.0.0/18 | AS4249 | LILLY-AS - Eli Lilly and Company | GB |
| 40.6.132.101 | 40.6.128.0/17 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.6.132.66 | 40.6.128.0/17 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
| 40.6.132.67 | 40.6.128.0/17 | AS4249 | LILLY-AS - Eli Lilly and Company | US |
WHOIS identity
No WHOIS records are currently associated with am.lilly.com in WhisperGraph.
Subdomains
75,413 observed subdomains of am.lilly.com.
Showing 25 of 75,413. View all subdomains →
Threat posture
History
Mail and authentication
SPF policy
7 SPF mechanisms authorising senders for am.lilly.com.
| Mechanism | Target |
|---|---|
| SPF_EXISTS | %{i}.spf.hc1959.iphmx.com |
| SPF_INCLUDE | _spf.salesforce.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | cust-spf.exacttarget.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | spf1.am.lilly.com |
| SPF_INCLUDE | spf2.am.lilly.com |
Related pages
Pivot deeper into the graph from am.lilly.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "am.lilly.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.