Hostname
lmex.io
Last fetched
lmex.io resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
lmex.io resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 18.154.219.104 | 18.154.216.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.154.219.126 | 18.154.216.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.154.219.4 | 18.154.216.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.154.219.45 | 18.154.216.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.85.31.44 | 52.85.28.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.85.31.57 | 52.85.28.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.85.31.65 | 52.85.28.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.85.31.93 | 52.85.28.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:146
- Organization
- domains by proxy,
- Contact emails
- —
Subdomains
1 observed subdomain of lmex.io.
| Subdomain |
|---|
| www.lmex.io |
Web-graph footprint
Distinct hostnames that link to or from lmex.io in the public web crawl.
38 sites link to this hostname.
1 site linked to from this hostname.
Sample inbound links
- kb.marketmaker.cloud
- test.lmex.io
- rocket.seo-anomaly-anchor.online
- rocket.seo-anomaly-conversion.online
- rocket.seo-anomaly-crawlbudget.online
- rocket.seo-anomaly-crawling.online
- rocket.seo-anomaly-ctr.online
- rocket.seo-anomaly-domain.online
- rocket.seo-anomaly-engagement.online
- rocket.seo-anomaly-hreflang.online
Sample outbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for lmex.io.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | _spf.mlsend.com |
| SPF_INCLUDE | mailgun.org |
Related pages
Pivot deeper into the graph from lmex.io.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "lmex.io"})-[: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.