Hostname
vlex.com.mx
Last fetched
vlex.com.mx resolves to 13.227.192.29, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. vlex.com.mx is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.227.192.29
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.48
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.69
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.84
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.35.78.109
- 13.35.78.3
- 13.35.78.30
- 13.35.78.74
- 3.166.181.118
3.166.176.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 3.166.181.122
3.166.176.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 3.166.181.28
3.166.176.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 3.166.181.66
3.166.176.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 52.222.136.42
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.222.136.5
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.222.136.59
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.222.136.81
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.173.161.42
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.173.161.35
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.173.161.81
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.173.161.50
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
IPv6 resolution
No AAAA record for vlex.com.mx is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:akky (una division de nic mexico)
- Registrant organisation
- vlex networks sl
Subdomains
Showing 12 of 19. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-482.awsdns-60.com
- ns-887.awsdns-46.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1209.awsdns-23.org
- ns-1662.awsdns-15.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
- aspmx4.googlemail.com
- aspmx5.googlemail.com
SPF policy
- include: aspmx.googlemail.com
- include: spf.mandrillapp.com
- a: vlex.com
- ip: 174.129.145.90
- ip: 87.236.247.6
Threat-feed evidence
History
Related pages
Pivot from vlex.com.mx into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "vlex.com.mx"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.