Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
The domain screenconnect-evite.one returned an HTTP 502 status code on 2026-10-01, indicating a server error at that time. It was also listed on two external blocklists, MetaMask and SEAL, as of 2026-10-02.
Recorded Evidence
On 2026-09-10, VirusTotal reported 16 detections out of 89 scanners for screenconnect-evite.one. The domain appeared in three OTX pulses on the same date. As of 2026-10-02, it was included on both the MetaMask and SEAL external blocklists. An internal listing was also present in the Phishdestroy system. The domain was first observed on 2026-08-31.
Interpretation
These records show that multiple independent sources flagged screenconnect-evite.one within a short period. The presence on several blocklists and the number of VirusTotal detections suggest that the domain attracted attention from threat intelligence and security platforms. The HTTP 502 response indicates server-side issues but does not clarify the domain's content or intent.
Recommended Actions
Review all available records for screenconnect-evite.one from VirusTotal, MetaMask, SEAL, OTX, and Phishdestroy to inform further investigation. Preserve these source listings for future reference and comparison. Monitor for additional updates from these sources to track any changes in status or new observations.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='screenconnect-evite.one', port=80): Max retries exceeded with url: / (Caused by NewConnect
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.
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-11 01:26:16 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:18: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.
Last analyzed First positive detection Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
カスペルスキー
LevelBlue
Lionic
SOCRadar
ソフォス
VIPRE
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.
Domain Status Transition2026-09-10 22:17:54 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-10 22:00:28 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-10 16:13:18 UTC
Domain ingestion complete. Initial state is marked as alive.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
14 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.
(US)
PhishDestroy Investigation
