telexxvb[.]com
“400 No required SSL certificate was sent”
PhishDestroy first observed telexxvb.com on Aug 25, 2026. The captured page title is “400 No required SSL certificate was sent”. Current evidence score: 65/100 (high).
Positive findings are stored from 2 sources: VirusTotal and URLQuery. VirusTotal recorded 3 detections among 91 engines: alphaMountain.ai, Fortinet, Kaspersky on Aug 25, 2026 at 04:38 UTC. URLQuery recorded 2 detections; no observation timestamp was retained. Non-positive and contextual checks: AlienVault OTX listed 4 community pulse references (not vendor detections) on Aug 25, 2026 at 04:40 UTC. The separate external-blocklist snapshot contained no matches on Aug 25, 2026 at 02:20 UTC. Google Safe Browsing returned no flag on Aug 25, 2026 at 04:39 UTC. URLScan captured the page on Aug 25, 2026 at 03:02 UTC.
The collector marked the hostname reachable on Aug 25, 2026 at 03:02 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Aug 25, 2026 at 01:02 UTC. Registration records for the domain list NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar and Jun 10, 2026 as the creation date. At collection time, the hostname resolved to 27.124.47.186. The stored server header is nginx/1.18.0 (Ubuntu). The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Telegram as the certificate issuer with validity through Sep 14, 2028; checked Aug 25, 2026 at 04:02 UTC.
The content indicators and 2 positive source findings support the current phishing classification. The stored fields do not identify an impersonated brand or victim interaction.
Network Security Intelligence Registrar context
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Latest Classified Outcome 2026-08-25 03:02:12 UTC
VirusTotal Analysis
Evidence & External Reports
Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive