Hostname
los40.com.gt
Last fetched
los40.com.gt resolves to 108.128.170.22, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. los40.com.gt is listed by 3 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 3 threat feeds. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 3
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:20 GMT
- Last seen on a feed
- Wed, 11 Nov 2026 17:51:45 GMT
Nutrition Label
Resolution chain
- 108.128.170.22
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.129.57.166
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.133.104.172
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.133.37.149
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.133.43.142
108.128.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.202.59.93
18.202.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.202.97.243
18.202.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.203.168.246
18.202.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.240.23.227
34.240.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.247.0.194
34.240.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.247.98.166
34.240.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.249.66.221
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.250.247.242
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 34.254.123.90
34.248.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 46.137.17.223
46.137.0.0/17 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.17.206.90
52.16.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.208.217.107
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.209.193.160
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.209.205.227
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 52.210.19.127
52.208.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
IPv6 resolution
No AAAA record for los40.com.gt is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for los40.com.gt. 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.
Company
- Company
- LOS40
- Industry
- Radio and Television Broadcasting
- Headquarters
- Guatemala
Technology
LOS40 has been observed using 41 technologies somewhere in its estate. This is observed use, not an exposure finding. The 20 most widely adopted:
- jQuery · javascript libraries
- Open Graph · content management system
- PHP · programming languages
- WordPress · blogs
- MySQL · database
- JSON-LD · frameworks and libraries
- Cloudflare · content delivery network
- Bootstrap · software framework
- Sitelinks Search Box · web tools and plugins
- reCAPTCHA · captcha
- Amazon Web Services · cloud hosting
- Yoast SEO · search engines
- Facebook · social media analytics and monitoring
- Cloudflare Bot Management · security
- Swiper · javascript libraries
- Shopify · e-commerce
- YouTube · online community software
- html5media · audio, video, graphics
- Office 365 · communication and collaboration
- jQuery UI · javascript libraries
Domain portfolio
Parent company's domain: los40.com (Los40)
Subdomains
| Subdomain |
|---|
| play.los40.com.gt |
| playertop.los40.com.gt |
| pre.los40.com.gt |
| sdmedia.los40.com.gt |
| smetrics.los40.com.gt |
| www.los40.com.gt |
Showing 6 of 6 subdomains (6 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
DNS signals
- The zone's primary nameserver (its SOA record) is not among its published nameservers.
Nameservers
- ns0.dnsmadeeasy.com
- ns1.dnsmadeeasy.com
- ns2.dnsmadeeasy.com
- ns3.dnsmadeeasy.com
- ns4.dnsmadeeasy.com
MX records
- poster1i.iberlayer.com
- poster2i.iberlayer.com
- poster3i.iberlayer.com
- poster4i.iberlayer.com
SPF policy
- ip: 66.165.183.0/24
- ip: 66.175.96.0/24
- include: spf.protection.outlook.com
- mx: los40.com.gt
Threat-feed evidence
History
Related pages
Pivot from los40.com.gt into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN) WHERE conflict.name IS NOT NULL
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.