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.
securecryptoexchange.xyz was recorded with multiple security observations on 2026-10-13, including a VirusTotal scan with detection results. The domain is also listed in the PhishDestroy internal catalogue as of the same date.
Recorded Evidence
VirusTotal checked securecryptoexchange.xyz on 2026-10-13, documenting 3 detections out of 92 scanners. OTX recorded two pulses for the domain on 2026-10-13. The domain registration date is listed as 2026-09-21 with NameSilo, LLC as the registrar. PhishDestroy internally listed the domain on 2026-10-13. A PageSpeed performance score of 82 was also recorded on 2026-10-13.
Interpretation
The VirusTotal record contains a scan-based measurement of detections by multiple security engines, reflecting how the domain was classified by those scanners on the checked date. PhishDestroy provides an internal listing, which documents that the domain was catalogued in their system. OTX records pulses, which are user-contributed security intelligence entries, offering another perspective on the domain's history. These sources together provide a snapshot of how securecryptoexchange.xyz was referenced in several security intelligence systems at the time of observation.
Recommended Actions
For securecryptoexchange.xyz, retain the VirusTotal detection record and OTX pulse entries for ongoing reference. Compare future VirusTotal and OTX results to these stored records to monitor for changes. Preserve the PhishDestroy listing as an internal reference point. Use these dated observations to inform any further technical review or network monitoring involving the domain.
登録情報作成日 2026年9月21日 (21d · Very New!)—Expires 2027年9月21日
技術詳細Provenance & timestamps
初確認2026年10月13日
Submitted URLhttps://securecryptoexchange.xyz/
Favicon Hash
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
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.
Certificate fingerprint474c829d699aa0588854ba6454dc0c52fa218ea24503272d14802e1b5ffe1b89Certificate names · 1 SANs
www.securecryptoexchange.xyz
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
Secure crypto exchange made simple: clear answers, a step-by-step guide and FAQ for 2026, from Securecryptoexchange. Understand secure crypto exchange and exactly what to do next.
対応 HTTP 200
HTML body 19.0 KB
Compressed 6.2 KB
Links 17 internal · 4 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.24.0 (Ubuntu)
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Open Graph description:Secure crypto exchange made simple: clear answers, a step-by-step guide and FAQ for 2026, from Securecryptoexchange. Understand secure crypto exchange and exactly what to do next.
Saved response-header values · 9
Accept-Ranges
bytes
Connection
keep-alive
Content-Encoding
gzip
Content-Length
6369
Content-Type
text/html
Date
Tue, 13 Oct 2026 11:29:50 GMT
Etag
"6ab3bfe1-18e1"
Last-Modified
Wed, 23 Sep 2026 12:02:41 GMT
Server
nginx/1.24.0 (Ubuntu)
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
2 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-13 13:29:52 UTC
情報源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Sitemap
Reachable (legacy)/sitemap.xml
HTTP response
200
Observed at
2026-10-13 13:29:52 UTC
情報源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
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 11:30:53 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 107.189.15.173.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
9 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
