VirusTotal
5 / 91 engine detections
Open report“Glo Finances”
5 / 91 engine detections
Open reportDBL_PHISH
4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
glofinances.com returned HTTP status 200 during the check on 2026-10-01, a dated record of one successful web response. The domain was registered on 2024-06-21 through Atak Domain Bilgi Teknolojileri A.S., and the SSL certificate was issued by Let's Encrypt / YE1 as scanned on 2026-09-23.
The HTTP check on 2026-10-01 recorded status 200 for glofinances.com. VirusTotal, checked on 2026-10-01, reported 5 detections across 91 scanners. OTX, checked on 2026-09-25, listed 4 pulses for the domain. The PhishDestroy internal listing recorded the domain, and PageSpeed returned a performance score of 85 on 2026-09-25. The IP address was recorded as 35.157.26.135 in DE, with AWS EC2 (eu-central-1) as the listed organization.
The HTTP and VirusTotal observations share the 2026-10-01 date, while OTX and PageSpeed were checked on 2026-09-25 and the SSL scan occurred on 2026-09-23. Because these named sources were collected on different dates, each value reflects only its own observation point rather than a single synchronized snapshot. Comparing the records requires keeping those dates attached to each value.
Retain the glofinances.com records with their exact dates so later observations can be compared against them. When new checks become available, compare each result to the corresponding dated entry rather than to a combined figure. Avoid submitting sensitive information to glofinances.com during any review of the collected evidence.
Edge-IP reputation is not attributed to this domain.
rosalyn.ns.cloudflare.cominbound-smtp.eu-west-1.amazonaws.compriority 10Location describes the IP network.
55026eb689eb3fe75319494152ddc6023fe54686371f40005ab1159332b71394www.glofinances.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.glofinances.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of glofinances.com · checked Sep 25, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
live_content→dns_inactive
dns_nxdomain
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
3→5
Reachable
No threat flag
View source5/91 engine detections
View source4 community references
View sourceglofinances.com
View source30 stored lookalike domains
2 community reports
CategoryOTHER_INVESTMENT_SCAM
Data submited by Intelligence for good
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
glofinances.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
glofinances.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.