Skip to security report
Analytics Dashboard
Domain security and threat intelligence
mail-accounts-verification.uw.ua favicon

mail-accounts-verification.uw.ua

In short

mail-accounts-verification.uw.ua is a credential phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). Registrar: ТОВ "Інтернет Інвест". Status: Last known active. Hosting: Railway. PhishDestroy sent 1 abuse report. VirusTotal: 5/92 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

“Sign in – Google Accounts”

Registrar
ТОВ "Інтернет Інвест"
Resolved IP
69.46.46.53
Registered
May 1, 2025
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 5/92 Automated brand label: Google Google Safe Browsing: threat flag recorded
Oct 23, 2026 1 Report Sent
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
5 / 92
engine detections
Google Safe Browsing
Flagged
URLQuery
2
detections
Page captures
10
open gallery
Domain age
540 days
Reports sent
1
view timeline
Source evidenceVirusTotal 5 / 92 · Google Safe Browsing: flagged 6 sources

VirusTotal

5 / 92 engine detections

Open report

Google Safe Browsing

Threat flag recorded

Open report

OTX

no community references

Open report

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

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
5 / 92
Page captures
10
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added mail-accounts-verification.uw.ua to its blocklist on 2026-10-23 after an intake check flagged it for social‑engineering according to Google Safe Browsing. The recorded page title was “Sign in – Google Accounts”. An HTTP 200 response was observed on the same date.

How the scam works

The detections correspond to a credential‑phishing pattern where a page imitates a Google login to lure users into submitting email addresses and passwords. Such pages rely on trusted branding to harvest credentials, but no specific data‑capture mechanism was observed in the captured snapshot.

Evidence

VirusTotal reported five detections on 2026-10-23, with four vendors marking the domain malicious and one marking it suspicious. Google Safe Browsing flagged the site as SOCIAL_ENGINEERING on 2026-10-23. urlscan.io recorded a malicious verdict with a score of 100 and categorized it as phishing targeting Google on 2026-10-23. Cloudflare Radar also returned a malicious phishing verdict on 2026-10-23. External blocklists showed no hits, and OTX listed zero pulses as of 2026-10-23.

Infrastructure

The recorded IP was 69.46.46.53 in the United States, associated with ASN 400940 (Railway). The domain used a CNAME to feqa063i.up.railway.app and presented a Let's Encrypt certificate issued on 2026-10-22 and valid until 2027-01-20. The domain age was recorded as zero days, while the apex registration was 273 days old. TLS was observed with a fresh certificate age of zero days.

What to do

Do not enter Google credentials on this site; if credentials were entered, change the password immediately and enable two‑factor authentication. Security teams should block the exact domain, monitor DNS and HTTP requests to it, and review authentication logs for possible compromise.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-23T01:54:21Z)URLScan screenshot (2026-10-22T12:12:38Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-10-23T03:41:44Z

Observed: · Retrieved:

Uuid
01a166d9-975e-7419-ab00-f42bfe908e80
Final url
https://mail-accounts-verification.uw.ua/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://mail-accounts-verification.uw.ua/",
        "from": "http://mail-accounts-verification.uw.ua/",
        "status": 307
    }
]
Ip
69.46.46.53
Contacted IP addresses
[
    "69.46.46.53"
]
Asns
[
    "400940"
]
Countries
[
    "US"
]
Linked domains
[
    "support.google.com",
    "accounts.google.com"
]
Document hash
67642199eaeb9749347b7ebc367838248df55950c6b7532ecdb0a85e1ab02f52
Script hashes
[
    "d46ce1862616cba61cd4c5b79a91ad489652769f17492af020a69ca0d38738a6",
    "948bd6d0fb3b306cf63511d4af2b5a9d41f1d08229fe18555fc9acbf4297ead7",
    "ac5a4f9b4dbad17f4a5da36b2029d4e31fb8ed9c7fb29faf6c4c12ea437dbce5",
    "b5f9b5199b99ab6c141f4540f0b7d0fe803c4ecf6956849ecb6e59d3d439272e",
    "eea6b39f869163f666eee275603b8ec71f27f7ace6185d8218304a943e07a606",
    "bf721ab289c32caa3773c1b1fccf39cb9c9525277a743511a03171ecf879d1d6"
]
Globals
[
    "TURBOPACK",
    "__next_s",
    "__next_f",
    "next",
    "__webpack_hash__",
    "t"
]
Tls
{
    "san": [
        "mail-accounts-verification.uw.ua"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "mail-accounts-verification.uw.ua",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-20T11:12:52Z",
    "valid_from": "2026-10-22T11:12:53Z"
}
Domain age days
0
Apex age days
273
Tls age days
0
Tls valid days
89
Requests
12
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 80,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "google"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Google"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "railway-hikari",
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "no-referrer"
}
Cloudflare Radar · 2026-10-23T01:54:21Z

Observed: · Retrieved:

Uuid
ec6c73aa-a6c4-4232-a6c0-42cadc4175dc
Final url
https://mail-accounts-verification.uw.ua/
Status
200
History
[
    {
        "url": "https://mail-accounts-verification.uw.ua/",
        "status": 200
    }
]
DOM structure hash
9daf1119407417acd11218bee2bf5011c49ef8496c962dfe88dafc76ac947ae6
Document hash
67642199eaeb9749347b7ebc367838248df55950c6b7532ecdb0a85e1ab02f52
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "mail-accounts-verification.uw.ua",
        "type": "CNAME",
        "value": "feqa063i.up.railway.app"
    },
    {
        "name": "mail-accounts-verification.uw.ua",
        "type": "CNAME",
        "value": "feqa063i.up.railway.app"
    }
]
Dnssec valid
false
Ip
69.46.46.53
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Internet Invest LLC",
    "created": "2025-05-01T17:32:25Z",
    "updated": "2026-05-11T15:30:09Z",
    "expires": "2027-05-01T17:32:25Z",
    "nameservers": [
        "mitch.ns.cloudflare.com",
        "zara.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-22T21:50:13Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 51,
    "malicious": 4,
    "suspicious": 1,
    "undetected": 36
}
Vendor labels
{
    "DNS8": "suspicious",
    "Webroot": "malicious",
    "Netcraft": "malicious",
    "Kaspersky": "phishing",
    "Google Safe Browsing": "phishing"
}
Reputation
0
Registrar
ua.imena
Expires
2027-05-01T17:32:25Z
First seen
2026-10-22T12:20:09Z
DNS records
[
    {
        "ttl": 60,
        "type": "A",
        "value": "69.46.46.53"
    },
    {
        "ttl": 300,
        "type": "CNAME",
        "value": "feqa063i.up.railway.app"
    }
]
Dns at
2026-10-22T21:56:46Z
Jarm
29d3fd00029d29d00042d43d00041d598ac0c1012db967bb1ad0ff2491b3ae
Certificate
{
    "san": [
        "mail-accounts-verification.uw.ua"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "6a5389d36099170feacc2e2d2fd1db25718",
    "sha256": "e23001f2ab7c8862c05c2bf844df0da8e930fa04126909d75462aacfee7968c2",
    "subject": "mail-accounts-verification.uw.ua",
    "valid_to": "2027-01-20T11:12:52Z",
    "valid_from": "2026-10-22T11:12:53Z"
}
Registration record
{
    "registrar": "ua.imena"
}
Website checks · 2026-10-23T01:55:35Z
Caa records
{
    "domain": "mail-accounts-verification.uw.ua"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Crawler rules
{
    "present": true
}
Page title and metadata
{
    "title": "Sign in – Google Accounts",
    "robots": "noindex, nofollow, nocache"
}
Trackers
{
    "requests": 11
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 79,
        "tls": 58,
        "wait": 69,
        "connect": 32,
        "download": 2
    },
    "response_ms": 240
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 16393,
    "co2_grams": 0.0006,
    "cleaner_than": 61
}
Dns server
{
    "ns": [
        {
            "ip": "173.245.58.148",
            "host": "zara.ns.cloudflare.com"
        },
        {
            "ip": "172.64.33.208",
            "host": "mitch.ns.cloudflare.com"
        }
    ],
    "zone": "uw.ua"
}
Location
{
    "ip": "69.46.46.53",
    "asn": "400940",
    "org": "Railway",
    "city": "Seattle",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "mail-accounts-verification.uw.ua"
}
DNS records
{
    "A": [
        "69.46.46.53"
    ],
    "CNAME": [
        "feqa063i.up.railway.app"
    ]
}
Dnssec
{
    "ds": true,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "no-referrer",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "69.46.46.53",
    "family": 4
}
Redirects
{
    "chain": [
        "https://mail-accounts-verification.uw.ua"
    ]
}
Page links
{
    "external": [
        "https://support.google.com/accounts",
        "https://accounts.google.com/TOS",
        "https://accounts.google.com/TOS"
    ],
    "external_count": 3
}
Registration record
{
    "registrar": "Internet Invest LLC",
    "created": "2025-05-01T17:32:25Z",
    "updated": "2026-05-11T15:30:09Z",
    "expires": "2027-05-01T17:32:25Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "mitch.ns.cloudflare.com",
        "zara.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "railway-hikari",
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "no-referrer"
    }
}

Questions about mail-accounts-verification.uw.ua

Is mail-accounts-verification.uw.ua legit?

No. PhishDestroy classifies mail-accounts-verification.uw.ua as a credential phishing page (risk: critical, 100/100); it was first detected on 2026-10-23. VirusTotal: 5/92 engines flag it. Google Safe Browsing flags it. Treat the site as unsafe.

Is mail-accounts-verification.uw.ua safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on mail-accounts-verification.uw.ua. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used mail-accounts-verification.uw.ua?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 10 captures

Primary capture 1 / 10
SourcePrimary capture
Recorded2026-10-23 03:42 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://mail-accounts-verification.uw.ua/
Position1 / 10
Open capture Wayback Download

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Google report ↗
Google Safe Browsing Flagged Social engineering checked Oct 23, 2026
IP Reputation abuse score 0/100 0 reports checked Oct 23, 2026
Registrar (base domain) ТОВ "Інтернет Інвест"
Abuse contactabuse@railway.app, abuse@imena.ua
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for uw.ua →
Registration (base domain)uw.ua · Created May 1, 2025 — Expires May 1, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 88/1002 brand signals
Submitted URLhttp://mail-accounts-verification.uw.ua/
Favicon Hash
Case ID
Observed page title
Sign in – Google Accounts
Automated brand references
Gmail Google
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 88 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
69.46.46.53
Network ASN
AS400940
Organization
Railway
Observed location
Seattle, US
Server header
railway-hikari

Nameservers 2

  • mitch.ns.cloudflare.com
  • zara.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-10-22 11:12:53
Valid until
2027-01-20 11:12:52
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte23001f2ab7c8862c05c2bf844df0da8e930fa04126909d75462aacfee7968c2
Certificate names · 1 SAN
  • mail-accounts-verification.uw.ua

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

viewdns.info · 69.46.46.53rapiddns.io

Latest Classified Outcome 2026-10-23 11:24:09 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-23 11:24:09 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 11:24:09 UTC last content: 2026-10-23 11:24:09 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed
DNS8
Google Safe Browsing
Kaspersky
Netcraft
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of mail-accounts-verification.uw.ua · checked Oct 23, 2026

99
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.97s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
3ms
Total Blocking Time
SI
2.25s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://mail-accounts-verification.uw.ua/
Final URL: https://mail-accounts-verification.uw.ua/
Sign in – Google Accounts
Response
HTTP 200
HTML body
16.0 KB
Compressed
4.1 KB
Links
0 internal · 3 external
Detected technologies
react
Selected response headers
Cache-Control: no-store
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: railway-hikari
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 15
Cache-Control
no-store
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 23 Oct 2026 02:05:54 GMT
Link
; rel=preload; as="font"; crossorigin=""; type="font/woff2", ; rel=preload; as="font"; crossorigin=""; type="font/woff2", ; rel=preload; as="image"
Referrer-Policy
no-referrer
Server
railway-hikari
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
X-Content-Type-Options
nosniff
x-hikari-trace
ams1.cycp
x-railway-edge
ams1
x-railway-request-id
MVARlwrdQ-KwYKmU0-QtfA
x-robots-tag
noindex, nofollow

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content 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.

Stored observation history2

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

    content_served

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

Recorded activity

5 entries
  1. Abuse report sent

    PD-20261023-F98C74

    abuse@railway.app
  2. URLScan

    Page captured

    View source
  3. Google Safe Browsing

    Threat flag recorded

    View source
  4. VirusTotal

    5/92 engine detections

    View source
  5. Added to PhishDestroy

    mail-accounts-verification.uw.ua

    View source

Check for cloaking

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

mail-accounts-verification.uw.ua

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 5 det. ChainPatrol URLQuery 2 det. Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-F98C74 Recipient: abuse@railway.app
Page title stored with report: Sign in – Google Accounts
PDF notice generated
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 mail-accounts-verification.uw.ua)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

Request a correction or appeal How PhishDestroy works
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/mail-accounts-verification.uw.ua"
  title="PhishDestroy threat report for mail-accounts-verification.uw.ua"
  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>