Security engines reporting a detection: 11. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 72H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@timeweb.ru.
The latest stored availability evidence still shows the domain reachable; 3 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
On 2026-10-10, breezart-russia.ru was observed in a PhishDestroy internal listing, documenting its presence in a publisher-managed catalogue. The domain was registered with TIMEWEB-RU on 2018-01-19, establishing a technical history prior to its appearance in this listing.
Recorded Evidence
The PhishDestroy internal listing contains a record for breezart-russia.ru as of 2026-10-10. The domain was first observed on 2026-10-11 and its SSL certificate, issued by GlobalSign nv-sa / GlobalSign GCC R3 DV TLS CA 2020, was scanned on the same date. Registration details show the domain was registered with TIMEWEB-RU on 2018-01-19.
Interpretation
PhishDestroy provides a catalogue entry for breezart-russia.ru, recording its listing status on a specific date. This type of record documents the domain’s inclusion in an internal reference rather than measuring technical content or scanning for threats. The evidence also records the domain’s registration and SSL certificate scan, which together form a technical snapshot as of the documented dates.
Recommended Actions
For breezart-russia.ru, preserve the PhishDestroy internal listing record and SSL certificate scan for future comparison. Retain the registration information as a reference point when reviewing subsequent observations. Comparing these dated records can help track changes in the domain’s technical and listing status over time. Maintain all evidence to support ongoing monitoring.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
RegistrationCreated Jan 19, 2018 —Expires Jan 19, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 11, 2026
DOM Analysisanalyzed Oct 11, 2026score 98/100
Submitted URLhttp://breezart-russia.ru/
Favicon Hash
Case ID
Page Title
Breezart | Официальный веб-сайт дилера компании Breezart
TLS Certificate
Certificate hostname mismatch·
Issued by GlobalSign nv-sa / GlobalSign GCC R3 DV TLS CA 2020· stored validity ends in 80 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
5.23.51.236
Network ASN
AS9123
Organization
TIMEWEB Co Ltd.
Observed location
St Petersburg, RU
Server header
nginx/1.30.4
Nameservers 4
ns1.timeweb.ru
ns2.timeweb.ru
ns3.timeweb.org
ns4.timeweb.org
Mail routing 2 MX records
mx1.timeweb.rupriority 10
mx2.timeweb.rupriority 20
Location describes the IP network.
TLS certificate
Issuer
GlobalSign nv-sa / GlobalSign GCC R3 DV TLS CA 2020
Valid from
2026-06-17 11:51:01
Valid until
2027-01-02 11:51:01
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 01:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint987e56f5feae63641abad400d27936b183344eace8b852c8be06f589678dcdd6Certificate names · 1 SANs
timeweb.ru
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Captcha85% confidence
Attributionmechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCaptchaChallenge85%2026-10-13 22:10:13 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 22:10:13 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.
Google PageSpeed Insights — mobile performance audit of breezart-russia.ru· checked Oct 12, 2026
54
Needs Work
Performance
FCP
11.87s
First Contentful Paint
LCP
22.89s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
127ms
Total Blocking Time
SI
11.87s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Threat First Observed2026-10-10 22:12:34 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 5.23.51.236.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
breezart-russia.ru detected and queued for full analysis
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.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
6 evidence signal groups linked1 reports recordedLast 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.
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 →
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · breezart-russia.ru
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: TIMEWEB-RU6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(MY)
