Hostname
freedompop.mx
Last fetched
freedompop.mx resolves to 35.81.26.20, announced in 35.80.0.0/12 by AMAZON-02 - Amazon.com, Inc. in US. freedompop.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
- 35.81.26.20
35.80.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.238.176.145
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.239.129.193
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.37.196.111
52.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.187.162.95
54.186.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.201.216.122
54.200.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
IPv6 resolution
No AAAA record for freedompop.mx is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for freedompop.mx. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| my.freedompop.mx |
| soporte.freedompop.mx |
| web-cdn.freedompop.mx |
| www.freedompop.mx |
| zylus-uat.freedompop.mx |
Showing 5 of 5 subdomains (5 per page).
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-70.awsdns-08.com
- ns-1013.awsdns-62.net
- ns-1418.awsdns-49.org
- ns-1948.awsdns-51.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
- t4xbg5ymd2cuaddowfabbjyldyvs4yzqoga5hnnck3ypxrcmu7gq.mx-verification.google.com
Threat-feed evidence
History
Related pages
Pivot from freedompop.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: "freedompop.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.