crypto-profit.digital returned an HTTP status code 502 during a check on 2026-10-01, documenting a specific server response for that date. The domain was first observed on 2026-07-27, and several security sources have recorded activity related to it.
Recorded Evidence
An OTX check on 2026-08-15 noted 3 OTX pulses for crypto-profit.digital. VirusTotal recorded 13 detections out of 91 scanners on 2026-08-15, with observation time known set to false. The domain is listed in the PhishDestroy internal catalogue, and its registrar is Spaceship, Inc.
Interpretation
The records from OTX, VirusTotal, and PhishDestroy each represent distinct observations about crypto-profit.digital, reflecting separate aspects of its presence and activity. The HTTP 502 response is a technical record of a server reply, not a verdict on content or behavior. The dates provided allow comparison of when different sources recorded their findings, but do not indicate direct relationships between those findings.
Recommended Actions
For crypto-profit.digital, retain the OTX pulse record, VirusTotal detection count, HTTP response record, and PhishDestroy internal listing as separate files for future reference. Compare each source's records against subsequent checks from the same provider. Keeping these dated records will support ongoing review and help document any changes in observations over time.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='crypto-profit.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectio
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedJul 27, 2026
Favicon Hash
ICANN OVERSIGHT
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Nameservers 1
ns4.ultraprohost.com
Location describes the IP network.
Latest Classified Outcome 2026-10-10 20:20:48 UTC
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:13:14 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-08-10 04:32:30 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-10 04:32:30 UTC → 2026-09-30 16:14:55 UTC · 1,235.71hmidpoint estimate ≈ 2026-09-04 22:23:42 UTC · precision very low · basis bounded
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: 13 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
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-08 10:00:33 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-08-12 23:43:10 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
crypto-profit.digital detected and queued for full analysis
Jul 27, 2026
Cloudflare Radar Report
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 8, 2026
Time to First Unavailability
1036 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
2 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · crypto-profit.digital
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: Spaceship6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(US)
