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.
scrappyxrp.xyz was observed in a record from 2026-10-13, with a listing on the ScamSniffer external blocklist as a notable entry. The domain was also referenced by multiple security sources on different dates, providing a range of technical observations.
Recorded Evidence
On 2026-10-13, scrappyxrp.xyz appeared on the ScamSniffer blocklist and was internally listed by PhishDestroy. VirusTotal checked the domain on 2026-10-06, recording 1 detection out of 92 total scanners. OTX referenced scrappyxrp.xyz in 3 separate pulses as of 2026-10-13. The domain was registered through NameSilo, LLC on 2026-09-25.
Interpretation
The PhishDestroy internal listing documents that scrappyxrp.xyz was recognized in its system, which is a form of security intelligence record. VirusTotal’s entry provides a quantitative measurement of how many scanners detected the domain at the time of its check. OTX pulses reflect that the domain was referenced in multiple community-driven security intelligence collections. These records capture a snapshot of how the domain was viewed by different security sources on their respective dates.
Recommended Actions
For scrappyxrp.xyz, retain the ScamSniffer blocklist entry and the PhishDestroy internal listing as primary records for future reference. Compare the VirusTotal detection data and OTX pulse references to new observations to track any changes in security source reporting. Consult these source records when evaluating the domain in future security reviews.
登録情報作成日 2026年9月25日 (17d · Very New!)—Expires 2027年9月25日
技術詳細Provenance & timestamps
初確認2026年10月13日
Submitted URLhttps://scrappyxrp.xyz/
ケース 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.
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 11:56:41 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 11:56:41 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.
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:57:25 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:57:25 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:56:41 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.134.218.
脅威対応 Pipeline
ディスカバリー
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.
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
