Skip to security report
Domain security report
mekasa.pro favicon

mekasa.pro

“Verification Required”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 26/89 Spamhaus DBL: DBL_MALWARE Scam type: Credential Phishing
OTX: 7 refs Jul 8, 2026 CDN
API
Registrar
Global Domain Group
Resolved IP
104.21.23.171
Registered
Jul 5, 2026
2 sources
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 26. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

Spamhaus DBL
DBL_MALWARE
VirusTotal
VirusTotal
26 det.
OTX references
CF Radar
Malicious
URLScan
URLScan
Gridinsoft
1/100
TLS Certificate
Within stored validity dates
Google Trust Services · Hostname coverage not recorded
Age
3 mo
Observed status
Last known active 301
PhishDestroy
DestroyList
Listed

Source evidence

10 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

26 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Gridinsoft

1/100

Observation time not recorded
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_MALWARE

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

PhishStats

checked — no match recorded

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

7 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware

Evidence Summary

Critical
VirusTotal
26/89
OTX
7 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Analysis indicates that mekasa.pro is an active phishing domain targeting users with a fake verification page. The domain was registered on July 5, 2026, through Global Domain Group LLC, and currently resolves to the IP address 104.21.23.171. Infrastructure analysis reveals the use of Cloudflare services, including Cloudflare Browser Insights and HTTP/3, alongside a SSL certificate issued by Google Trust Services. The site’s page title, 'Verification Required,' aligns with common phishing tactics designed to deceive users into submitting sensitive information. The domain is flagged by five security blocklists, including MalwareFilter, PhishDestroy, StevenBlack, OISD, and Hagezi, and appears in five threat intelligence pulses on AlienVault OTX. As of July 12, 2026, 27 out of 95 security vendors on VirusTotal detect the domain as malicious, reinforcing its classification as a high-risk threat. The Gridinsoft trust score of 1/100 further corroborates its malicious nature. No specific brand impersonation or phishing kit details are currently available in the intelligence data, but the combination of recent registration, Cloudflare obfuscation, and widespread blocklisting suggests a deliberate attempt to evade detection while conducting fraudulent activity. Defenders should treat this domain as hostile and implement blocking measures at the network and endpoint levels. Users encountering this domain should avoid interaction, as the exact content and data collection methods remain unconfirmed but are likely designed to harvest credentials or personal information.

Data coverage & collection

20 · datasets with records / 11 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
26 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
7 · community references
External blocklists
0 · external matches
PhishStats
Dated lookup retained
Cloudflare Radar
maliciousCollection time not recorded
Gridinsoft
1/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
DBL_MALWARE
Domain registration
Global Domain Group LLCCollection time not recorded
Network & DNS
104.21.23.171 · 2 · nameserversCollection time not recorded
TLS certificate
Google Trust Services
Page captures
2 · retained captures
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
100/100 · mobile performance
Availability history
24 · stored state changes
Source observation history
6 · stored source events
IP reputation
Network-level observations
Not recorded in this report 11

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • DNS security filters
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Global Domain Group LLC · 104.21.23.171 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 130-12-181-1112026-0732-bit3c89c25-175-192-19754e64e9d2ca3activeall-domainsamadeyarkeistealerarmasciiblocklist+6 more
Registrar Global Domain Group US(US)
RegistrationCreated Jul 5, 2026 (104d) — Expires Jul 5, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedJul 8, 2026
DOM Analysisanalyzed Jul 10, 2026score 98/100
Submitted URLhttps://mekasa.pro/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.23.171
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2
  • amy.ns.cloudflare.com
  • bob.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-09-02 10:28:55
Valid until
2026-12-01 11:26:24
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-10 10:02:56 UTC
Collection source
PhishDestroy collector
Certificate fingerprint18476d03b2b2af7a594a3309dabdfed16f0f074a7404c31b912aa4485299ad8d

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-17 02:10:46 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-17 02:10:46 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 02:10:46 UTC
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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

26 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 26 detections
AILabs (MONITORAPP)
alphaMountain.ai
BitDefender
Certego
Chong Lua Dao
CRDF
CyRadar
Dr.Web
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Lumu
MalwareURL
Netcraft
PrecisionSec
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of mekasa.pro · checked Jul 13, 2026

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

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

Not observed No cloaking was observed in the stored scan

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Server header seen by scanner
cloudflare

Scanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://mekasa.pro/; server=cloudflare

Title shown to the security scanner301 Moved Permanently
Title shown to a browser visitorVerification Required
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-10-15 01:58:52 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  2. Domain Status Transition 2026-10-13 22:29:41 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  3. Domain Status Transition 2026-08-29 22:15:38 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  4. Domain Status Transition 2026-08-29 10:00:31 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  5. VirusTotal Detections Update 2026-07-12 22:17:06 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 25 to 27. Added scanner alerts: LevelBlue. Resolved alerts: PrecisionSec, SOCRadar, Seclookup, Sophos, URLQuery, Webroot.
  6. VirusTotal Detections Update 2026-07-08 18:54:59 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from None to 25. Added scanner alerts: BitDefender, CRDF, Certego, Chong Lua Dao, Cluster25, CyRadar, Dr.Web, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Lumu, MalwareURL, Netcraft, PrecisionSec, alphaMountain.ai.
Stored observation history30

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→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 25
  1. Availability monitor · Recorded state

    Unavailable→Reachable

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Reachable→Unavailable

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  17. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  19. Availability monitor · Recorded state

    inactive→Unknown

    probe_inconclusive

  20. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  21. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unavailable→Reachable

  23. Availability monitor · Recorded state

    Reachable→Unavailable

  24. VirusTotal · Detection count

    25→27

  25. VirusTotal · Detection count

    None→25

Threat Response Pipeline

Discovery
Analysis
Monitoring

16 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
mekasa.pro detected and queued for full analysis
Jul 8, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_MALWARE
Oct 9, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Jul 10, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
26/89 recorded on VirusTotal
Sep 12, 2026
OTX Community References
7 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 9, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as malware
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Jul 10, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Oct 15, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 301); the cause was not independently established.
Oct 14, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Aug 30, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 404); the cause was not independently established.
Aug 29, 2026
VT Detection +2
+2 new detections (25 → 27): LevelBlue
Jul 13, 2026
VT Detection +25
+25 new detections (0 → 25): BitDefender, CRDF, Certego, Chong Lua Dao +16
Jul 8, 2026
DestroyList Published
Jul 8, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 0 stored notification records Last known active

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 mekasa.pro)
  • 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
Read the evidence in context

About This Report: mekasa.pro

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Verification Required”.

VirusTotal detections for mekasa.pro: 26 (2026-09-12 02:27:25 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A 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/mekasa.pro"
  title="PhishDestroy threat report for mekasa.pro"
  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>