Hostname
mnyl.com.mx
Last fetched
mnyl.com.mx resolves to 3.219.78.25, announced in 3.208.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. mnyl.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
- 3.219.78.25
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.220.212.11
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.220.214.71
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.72.124.179
52.72.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.86.145.195
52.86.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for mnyl.com.mx is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:akky (una division de nic mexico)
- Registrant organisation
- seguros monterrey new york life s.a. de c.v.
Subdomains
Showing 12 of 17. 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
- dns03.monterrey-newyorklife.com.mx
- dns1.monterrey-newyorklife.com.mx
- dns2.monterrey-newyorklife.com.mx
- 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
MX records
- mx1.hc4038-43.iphmx.com
- mx2.hc4038-43.iphmx.com
SPF policy
- a: mx1.hc4038-43.iphmx.com
- a: mx2.hc4038-43.iphmx.com
- include: rp.oracleemaildelivery.com
- include: spf.qb-feedback.com
- include: _spf.qemailserver.com
- include: mailgun.org
- ip: 104.160.73.167
- ip: 200.77.236.185
- ip: 200.77.236.187
Threat-feed evidence
History
Related pages
Pivot from mnyl.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: "mnyl.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.