Skip to security report
Domain security and threat intelligence
glofinances.com favicon

glofinances.com

“Glo Finances”

Registrar
Atak Domain Bilgi Tekn…
Resolved IP
35.157.26.135
Registered
Jun 21, 2024
PhishDestroy assessment Critical
First observed Sep 17, 2026 16:40 UTC · PhishDestroy
VirusTotal detections: 5/91 Spamhaus DBL: DBL_PHISH Automated brand label: Lido
OTX: 4 refs Sep 17, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 5. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Domain age
Source evidenceVirusTotal 5 / 91 · OTX 4 references 5 sources

VirusTotal

5 / 91 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
5 / 91
OTX
4 community refs

AI-assisted evidence review

Assessment

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.

Recorded Evidence

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.

Interpretation

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.

Recommended Actions

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domain
IP Context Netlify shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptocrypto scamdomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Atak Domain Bilgi Tekn… TR(TR)
RegistrationCreated Jun 21, 2024 — Expires Jun 21, 2027
Technical detailsProvenance & timestamps
First DetectedSep 17, 2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
35.157.26.135
Network ASN
AS16509
Organization
AWS EC2 (eu-central-1)
Observed location
Frankfurt, DE
Server header
Netlify

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • rosalyn.ns.cloudflare.com

Mail routing 1 MX record

  • inbound-smtp.eu-west-1.amazonaws.compriority 10

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-20 01:53:47
Valid until
2026-12-19 01:53:46
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-23 16:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint55026eb689eb3fe75319494152ddc6023fe54686371f40005ab1159332b71394
Certificate names · 1 SANs
  • www.glofinances.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-18 08:21:15 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-19 01:29:44 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-06 10:11:49 UTC last content: 2026-10-06 10:11:49 UTC current episode first observed: 2026-10-06 22:13:39 UTC observed RIP window: 2026-10-06 10:11:49 UTC → 2026-10-06 22:13:39 UTC · 12.03h midpoint estimate ≈ 2026-10-06 16:12:44 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.glofinances.comDomain record

The original observation time is not recorded for these hostnames.

Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of glofinances.com · checked Sep 25, 2026

85
Needs Work
Performance
FCP
0.92s
First Contentful Paint
LCP
2.48s
Largest Contentful Paint
CLS
0.099
Cumulative Layout Shift
TBT
103ms
Total Blocking Time
SI
9.82s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
12.03
Estimate basis
Bounded by observations
Estimate precision
Medium

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history18

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 13
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    live_content→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. VirusTotal · Detection count

    3→5

  13. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    5/91 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Added to PhishDestroy

    glofinances.com

    View source

Lookalike domains

30 stored lookalike domains

ido.fi omission iido.fi homoglyph ildo.fi homoglyph kido.fi replacement ldio.fi transposition ldo.fi omission ledo.fi vowel-swap libo.fi homoglyph lico.fi replacement lid.fi omission lid0.fi homoglyph lida.fi vowel-swap
Show all (18)
liddo.fi repetition lidl.fi replacement lido-fi.com various lidoe.fi addition lidofi.com various lidoo.fi addition liido.fi repetition lilo.fi bitsquatting lio.fi omission liod.fi transposition liro.fi replacement lito.fi bitsquatting lldo.fi homoglyph llido.fi repetition ludo.fi replacement mido.fi bitsquatting nido.fi bitsquatting oido.fi replacement

Community intelligence

2 community reports

CategoryOTHER_INVESTMENT_SCAM

Data submited by Intelligence for good

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

glofinances.com

Evidence & External Reports

Third-Party Detection — ChainAbuse
2 reports filed for glofinances.com · category: Other Investment Scam · source checked
Flagged by Intelligence for Good on Sep 25, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Deep Analysis
Help & reporting

Were You Affected by This Site?

2 evidence signal groups linked 0 stored notification records Unverified

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including glofinances.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/glofinances.com"
  title="PhishDestroy threat report for glofinances.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>