bezopasnet.space was observed in a CryptoFirewall blocklist entry dated 2026-10-13, which records its inclusion on an external security list. The domain also received a high PageSpeed performance score, providing insight into its technical configuration.
Recorded Evidence
On 2026-10-13, bezopasnet.space was listed in the CryptoFirewall external blocklist. VirusTotal checked the domain on 2026-10-11 and documented 18 detections out of 92 total scanners. OTX pulses were recorded as 9 on 2026-10-13. The domain registration date is 2026-05-20, and it is registered with Registrar of Domain Names REG.RU LLC. The internal PhishDestroy listing was also active as of 2026-10-13.
Interpretation
PhishDestroy contains an internal listing for bezopasnet.space, which documents its presence in a monitored database. VirusTotal records the domain's detection count and scanner coverage, representing a technical assessment of its network presence. The evidence spans several sources and dates, offering a snapshot of external and internal security observations for comparison.
Recommended Actions
For bezopasnet.space, preserve the CryptoFirewall blocklist entry and VirusTotal detection records for ongoing reference. Compare OTX pulse counts and internal PhishDestroy listings to monitor changes in security intelligence. Retain source records to support future technical reviews and maintain a timeline of observed evidence for the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Certificate fingerprintc68bd69a04a2bfbd8407f16c46d89856b0a0953d9fb667ca1af84ead841a35d1Certificate names · 1 SANs
www.bezopasnet.space
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-13 00:04:50 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 00:04:50 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 bezopasnet.space· checked Oct 13, 2026
91
Good
Performance
FCP
1.56s
First Contentful Paint
LCP
3.41s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
10ms
Total Blocking Time
SI
1.56s
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-13 00:04:50 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 212.192.14.75.
위협 대응 Pipeline
발견
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
(SE)
