Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 11. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
duplicate-disabled-170698.invalid favicon

duplicate-disabled-170698.invalid

In short

PhishDestroy first recorded duplicate-disabled-170698.invalid on 2026-03-11. VirusTotal: 11/89 engines flag it.

“M2 Recovery - Protecting your Money”

Registrar
United StatesOpen Provider
Resolved IP
Germany79.133.41.250Ultahost, Inc. · CDN
First observed
Mar 11, 2026
PhishDestroy assessment Critical
88/100
Evidence score
Availability Server error The latest stored response was inconclusive Observed HTTP probe
VirusTotal detections: 11/89
VirusTotal
engine detections
URLScan
engine verdict · score 45
Page captures
open gallery
Mar 11, 2026 CDN
X Telegram API

Questions about duplicate-disabled-170698.invalid

Is duplicate-disabled-170698.invalid legit?

PhishDestroy rates duplicate-disabled-170698.invalid as critical risk (88/100) from the recorded evidence; it was first recorded on 2026-03-11. VirusTotal: 11/89 engines flag it. Treat the site as unsafe.

Is duplicate-disabled-170698.invalid safe to connect a wallet?

This report does not record which wallet requests duplicate-disabled-170698.invalid makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used duplicate-disabled-170698.invalid?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 11 / 89 9 sources

VirusTotal

11 / 89 engine detections

Open report

URLScan

Malicious · engine verdict · score 45

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

019cdab3-d2bd-71e0-80b0-c9ba79a3b361

Final URL

https://www.m2recovery.ca/

HTTP response

200

IP address

79.133.41.250

Reverse DNS (PTR)

cp1.fra1.ultacp.com

Contacted domains

  • m2recovery.com
  • ka-f.fontawesome.com
  • api.emailjs.com
  • www.google-analytics.com
  • www.googletagmanager.com
  • cdn.jsdelivr.net
  • fonts.googleapis.com

Contacted IP addresses

  • 216.239.36.178
  • 104.21.26.223
  • 142.250.195.232
  • 104.26.5.221
  • 167.99.194.202
  • 104.16.174.226
  • 79.133.41.250

Autonomous systems (ASN)

  • 15169
  • 13335
  • 14061
  • 214036

Server countries

  • US
  • GB
  • DE

Linked domains

  • client.m2recovery.ca
  • news.sky.com

Document hash

a0bda3a6eebd5300efaebc5b3f941e1a95f8d428c048fb4b673913431ade6c33

Script hashes

  • ccf00d1923b0131a10e0c6d26f95e5dee6ebf8621a27e83c5a2f68a2e0093142
  • c1764ddaae73ba49f767047be770a8d16e3e5a97585d395ae581b0934d9c771e
  • 31a224c969bb0eda1cd423ea5db82b787281a32bb44f8c5ccab93c3f39f8e992
  • 7b05e95a1af1886e06caee728e99569ae4a446a5396f03233a7b904bbc1220d5
  • f02c4d665c3c7f087013880482178a8a36e37754816b043e6c4ba838931b66fb
  • ca7dce2391845e8aec7da135f33fabd10f74eed28a532ac66fd01f761fcfb42f
  • 17b18307699b67e749b8eda9784d775fcf67142738da1eff34c33e04cac2ac08
  • 620bd01c4c002f0889fdc659369a7b16f69ab51e0972d53baefd0798e2e09469
  • a32f766f2db51e03c7b2ca639b479f52e620b26004302a5408ad3c59ac9aeefa
  • 13ff936ed73000ddb6726b5e04a8a023705d735cab4125898043f4717bcfc0e2

JavaScript globals

  • emailjs
  • templateParams
  • __cfQR
  • FontAwesomeKitConfig
  • $
  • jQuery
  • _wpemojiSettings
  • conditionizr
  • html5
  • Modernizr
  • yepnope
  • sibErrMsg
  • ajax_sib_front_object
  • sibVerifyCallback
  • Getwid
  • wp
  • wpcf7
  • dnd_cf7_uploader
  • nbcpf
  • wpcf7r
  • wpcf7_redirect
  • cf7mls_object
  • ghostkitVariables
  • GHOSTKIT
  • ScrollReveal
  • jarallax
  • VideoWorker
  • jarallaxVideo
  • Swiper
  • allowedBrowsers
  • SmoothScroll
  • pum_vars
  • pum_sub_vars
  • pum_popups
  • PUM
  • PUM_Accessibility
  • PUM_Analytics
  • pm_cookie
  • pm_cookie_json
  • pm_remove_cookie

Cookies

  • _ga_P5FM2SXSHG
  • _ga

Browser storage keys

  • modernizr
  • wpEmojiSettingsSupports

TLS session and certificate

Subject alternative names
  • m2recovery.ca
  • www.m2recovery.ca
Cipher
AES_128_GCM
Issuer
R13
Subject
www.m2recovery.ca
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

249

Registered domain age, days

249

Certificate age, days

1

Certificate validity, days

89

Page requests

93

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
45
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
LiteSpeed
Content-type
text/html
Original source fields · JSON
Uuid
019cdab3-d2bd-71e0-80b0-c9ba79a3b361
Final url
https://www.m2recovery.ca/
Status
200
Ip
79.133.41.250
Ptr
cp1.fra1.ultacp.com
Contacted domains
[
    "m2recovery.com",
    "ka-f.fontawesome.com",
    "api.emailjs.com",
    "www.google-analytics.com",
    "www.googletagmanager.com",
    "cdn.jsdelivr.net",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "216.239.36.178",
    "104.21.26.223",
    "142.250.195.232",
    "104.26.5.221",
    "167.99.194.202",
    "104.16.174.226",
    "79.133.41.250"
]
Asns
[
    "15169",
    "13335",
    "14061",
    "214036"
]
Countries
[
    "US",
    "GB",
    "DE"
]
Linked domains
[
    "client.m2recovery.ca",
    "news.sky.com"
]
Document hash
a0bda3a6eebd5300efaebc5b3f941e1a95f8d428c048fb4b673913431ade6c33
Script hashes
[
    "ccf00d1923b0131a10e0c6d26f95e5dee6ebf8621a27e83c5a2f68a2e0093142",
    "c1764ddaae73ba49f767047be770a8d16e3e5a97585d395ae581b0934d9c771e",
    "31a224c969bb0eda1cd423ea5db82b787281a32bb44f8c5ccab93c3f39f8e992",
    "7b05e95a1af1886e06caee728e99569ae4a446a5396f03233a7b904bbc1220d5",
    "f02c4d665c3c7f087013880482178a8a36e37754816b043e6c4ba838931b66fb",
    "ca7dce2391845e8aec7da135f33fabd10f74eed28a532ac66fd01f761fcfb42f",
    "17b18307699b67e749b8eda9784d775fcf67142738da1eff34c33e04cac2ac08",
    "620bd01c4c002f0889fdc659369a7b16f69ab51e0972d53baefd0798e2e09469",
    "a32f766f2db51e03c7b2ca639b479f52e620b26004302a5408ad3c59ac9aeefa",
    "13ff936ed73000ddb6726b5e04a8a023705d735cab4125898043f4717bcfc0e2"
]
Globals
[
    "emailjs",
    "templateParams",
    "__cfQR",
    "FontAwesomeKitConfig",
    "$",
    "jQuery",
    "_wpemojiSettings",
    "conditionizr",
    "html5",
    "Modernizr",
    "yepnope",
    "sibErrMsg",
    "ajax_sib_front_object",
    "sibVerifyCallback",
    "Getwid",
    "wp",
    "wpcf7",
    "dnd_cf7_uploader",
    "nbcpf",
    "wpcf7r",
    "wpcf7_redirect",
    "cf7mls_object",
    "ghostkitVariables",
    "GHOSTKIT",
    "ScrollReveal",
    "jarallax",
    "VideoWorker",
    "jarallaxVideo",
    "Swiper",
    "allowedBrowsers",
    "SmoothScroll",
    "pum_vars",
    "pum_sub_vars",
    "pum_popups",
    "PUM",
    "PUM_Accessibility",
    "PUM_Analytics",
    "pm_cookie",
    "pm_cookie_json",
    "pm_remove_cookie"
]
Cookies
[
    "_ga_P5FM2SXSHG",
    "_ga"
]
Storage keys
[
    "modernizr",
    "wpEmojiSettingsSupports"
]
Tls
{
    "san": [
        "m2recovery.ca",
        "www.m2recovery.ca"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "R13",
    "subject": "www.m2recovery.ca",
    "protocol": "TLS 1.3",
    "valid_to": "2026-06-07T17:49:41Z",
    "valid_from": "2026-03-09T17:49:42Z"
}
Domain age days
249
Apex age days
249
Tls age days
1
Tls valid days
89
Requests
93
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 45,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "LiteSpeed",
    "content-type": "text/html"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
019cdab3-d2bd-71e0-80b0-c9ba79a3b361
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

URLQuery

checked — no detections recorded

Open report

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

3c270631-6bec-493f-a80e-d865faed1bb4

Final URL

https://www.m2recovery.ca/

HTTP response

200

Navigation history

  • URL
    https://www.m2recovery.ca/
    Status
    200

DOM structure hash

66bc01879136c6b36105b5281af16eb77c54c3fe102dbdf85f9f4fbbaf15605e

Document hash

a0bda3a6eebd5300efaebc5b3f941e1a95f8d428c048fb4b673913431ade6c33

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    www.m2recovery.ca
    Type
    CNAME
    Value
    m2recovery.ca
  • Name
    m2recovery.ca
    Type
    A
    Value
    79.133.41.250

DNSSEC valid

No

IP address

79.133.41.250

Registration record

Registrar
Open Provider Inc.
Registered
Updated
Expires
Nameservers
  • hugh.ns.cloudflare.com
  • nadia.ns.cloudflare.com
Original source fields · JSON
Uuid
3c270631-6bec-493f-a80e-d865faed1bb4
Final url
https://www.m2recovery.ca/
Status
200
History
[
    {
        "url": "https://www.m2recovery.ca/",
        "status": 200
    }
]
DOM structure hash
66bc01879136c6b36105b5281af16eb77c54c3fe102dbdf85f9f4fbbaf15605e
Document hash
a0bda3a6eebd5300efaebc5b3f941e1a95f8d428c048fb4b673913431ade6c33
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "www.m2recovery.ca",
        "type": "CNAME",
        "value": "m2recovery.ca"
    },
    {
        "name": "m2recovery.ca",
        "type": "A",
        "value": "79.133.41.250"
    }
]
Dnssec valid
false
Ip
79.133.41.250
Registration record
{
    "registrar": "Open Provider Inc.",
    "created": "2025-07-04T19:53:59Z",
    "updated": "2025-09-02T19:57:28Z",
    "expires": "2026-07-04T19:53:59Z",
    "nameservers": [
        "hugh.ns.cloudflare.com",
        "nadia.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

Gridinsoft

No report found

Open report
Stored collection fields

A missing report is not a trust verdict. Legacy zeroes remain in the stored record; the measured trust score is unavailable.

normalized_record
{"trust_score":null,"status":"not_found","signals":[],"report_url":null,"observed_at":null,"rating":null,"review_count":0,"request_url":"https://gridinsoft.com/online-virus-scanner/url/www-m2recovery-ca"}
stored_record
{"gs_trust_score":0,"gs_status":"not_found","gs_signals":null,"gs_url":"https://gridinsoft.com/online-virus-scanner/url/www-m2recovery-ca","gs_rating":null,"gs_reviews":0}

PhishDestroy DOM

88 / 100 · heuristic score · 0 brand references · 1 classification

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 4 captures

All capture links and hashes (4)
Observed page title
M2 Recovery - Protecting your Money
TLS Certificate
Issued by Let's Encrypt / R13
duplicate-disabled-170698.invalid: caution — 11/89 VirusTotal engines. PhishDestroy risk score 88/100 (critical).
Social preview card duplicate-disabled-170698.invalid: caution — 11/89 VirusTotal engines. PhishDestroy risk score 88/100 (critical). v eefe6fdbcb73

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 45 report ↗
IP Context Germany79.133.41.250 CDN shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Hosting abuse contact u-abuse@ultahost.com ULTAHOST-AS Ultahost, Inc., US · AS214036
RegistrationExpires Jul 4, 2026
Time to First Unavailability 4 days
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 DetectedMar 11, 2026
DOM Analysisanalyzed Jul 10, 2026score 88/100
Submitted URLhttps://www.m2recovery.ca/
Favicon Hash
Case ID
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

Shared CDN edge
Resolved IP
Germany79.133.41.250
Network ASN
AS214036
Organization
Ultahost, Inc.
Observed location
GermanyMörfelden-Walldorf, DE
Server header
LiteSpeed

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • nadia.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / R13
Valid from
2026-03-09 17:49:42
Valid until
2026-06-07 17:49:41
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-15 05:47:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint3d5f3406d5f1a0ddf63039fd0e9710a8a7c88b2928b8a7a209999cf307c41307
Certificate names · 1 SAN
  • m2recovery.ca

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Technologies · 17 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

11 / 89 security vendors flagged this domain
View on VT
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Fortinet
G-Data
Gridinsoft
Lionic
Sophos
VIPRE

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of duplicate-disabled-170698.invalid · checked Mar 11, 2026

62
Needs Work
Performance
FCP
3.9 s
First Contentful Paint
LCP
7.66 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
35 ms
Total Blocking Time
SI
6.36 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Captured network requests

Network requests: 93 SHA-256 hashes: 87 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 05:25 UTC.

Open this scan on URLScan 019cdab3-d2bd-71e0-80b0-c9ba79a3b361 ↗

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Domain monitor · Recorded state

    Reachable→Unavailable

All retained availability observations32

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:14:59.000000
    Evidence SHA-256
    d44b1f74fe6ceee5495d027fc9b50171d026db922b672033f53e63031a37f7b2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:14:59
    Evidence reason
    unavailable
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:14:59.000000
    Evidence SHA-256
    d44b1f74fe6ceee5495d027fc9b50171d026db922b672033f53e63031a37f7b2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:14:59
    Evidence reason
    unavailable
  3. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:16:10.000000
    Evidence SHA-256
    cd1f25d4733176ceb02b8b5d60c217c99e86cfb00943966f53d7ff91e1b87331
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 03:16:10
    Evidence reason
    unavailable
  4. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:16:10.000000
    Evidence SHA-256
    cd1f25d4733176ceb02b8b5d60c217c99e86cfb00943966f53d7ff91e1b87331
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 03:16:10
    Evidence reason
    unavailable
  5. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:24:58.000000
    Evidence SHA-256
    8b542764f1f5f12301aeb0809c674c41844da7adb06f8cd796baee91201c9952
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 03:24:58
    Evidence reason
    unavailable
  6. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:24:58.000000
    Evidence SHA-256
    9d416c4834b5d0280f3215deca299bcc5b093a13d7a9b3f8c30cc49ba98fcb8a
    Evidence timestamp as recorded
    2026-10-29 03:24:58
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  7. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 03:25:55.000000
    Evidence SHA-256
    a439b7169d2a8a2e57f5e4886299212dc02e6f5cfa0504a40b302169bd201345
    Evidence timestamp as recorded
    2026-10-27 03:25:55
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  8. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 03:25:55.000000
    Evidence SHA-256
    dab281b6ebd8b45c98fb14c8cad06264ee727461714de6e39e6edcbfbe9830ce
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 03:25:55
    Evidence reason
    unavailable
  9. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:22:02.000000
    Evidence SHA-256
    ba8f10f202c1a1381373d59e5f9c1be1df855a18d07b21f2d247af3ec5d9f7a1
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 03:22:02
    Evidence reason
    unavailable
  10. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:22:02.000000
    Evidence SHA-256
    bc4ef1d18fc4c342d49f86972945232b8cce5efc21bc0d30afd942d90a458623
    Evidence timestamp as recorded
    2026-10-25 03:22:02
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  11. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 03:26:38.000000
    Evidence SHA-256
    8358e41cec711f2a9990821b7b69fcf00f838ab01abf4a3919c9316c6138190c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 03:26:38
    Evidence reason
    unavailable
  12. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 03:26:38.000000
    Evidence SHA-256
    8b34f820a271b21c89abd38957fb846eaf5a8c268aa261497dc906ee642352d5
    Evidence timestamp as recorded
    2026-10-23 03:26:38
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  13. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 03:16:29.000000
    Evidence SHA-256
    e5e52063e33daecd1f800e3b6b3b6ccd7e32b83e8ba66bcb9230db80fbf5fd80
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 03:16:29
    Evidence reason
    unavailable
  14. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-21 03:16:29.000000
    Evidence SHA-256
    fdc7fd5a36bc2e3770c1e3a13cfcf4927743e8a39535b938f71bd590c5f46d1e
    Evidence timestamp as recorded
    2026-10-21 03:16:29
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  15. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 03:16:17.000000
    Evidence SHA-256
    4564365f4ff8003ef0190d6d7c0a892714511c0d0303e9005f393a0ae7d35c2e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 03:16:17
    Evidence reason
    unavailable
  16. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-19 03:16:17.000000
    Evidence SHA-256
    c937ce0acc3df7ef8426c6f18cff422c53cd7b69440c7a8d3f1042552b067370
    Evidence timestamp as recorded
    2026-10-19 03:16:17
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  17. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-17 03:15:31.000000
    Evidence SHA-256
    1a3476e38dbc42897007fb4a84fee98d532a04632be3af8d0b3436e35277dde4
    Evidence timestamp as recorded
    2026-10-17 03:15:31
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  18. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-17 03:15:31.000000
    Evidence SHA-256
    21ced04fcf9b2431d66ebf474515d6b651a6580a1a07547b0962bd9fb2af1b4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-17 03:15:31
    Evidence reason
    unavailable
  19. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-15 03:16:24.000000
    Evidence SHA-256
    08b839373015d6c0398500b94ef4ccaeebae7b7f7c488f86356b7f25310548ad
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-15 03:16:24
    Evidence reason
    unavailable
  20. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-15 03:16:24.000000
    Evidence SHA-256
    a8efa84a7121c13f6c697090c7859720d2d1e2a0bfdb1242ee8e1fa985a7b673
    Evidence timestamp as recorded
    2026-10-15 03:16:24
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  21. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-13 03:31:44.000000
    Evidence SHA-256
    84d8c5d2fabca54b95e8bb30d11e88c31b8568931098639bf3d30e68b7b93cb9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-13 03:31:44
    Evidence reason
    unavailable
  22. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-13 03:31:44.000000
    Evidence SHA-256
    e46cf34329d84e55e22d89bbf4f52e00a0c9294e44d85244fd52ea511d114850
    Evidence timestamp as recorded
    2026-10-13 03:31:44
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  23. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-11 03:31:03.000000
    Evidence SHA-256
    3c88659168bc7911b285c29b451e6146b18014579e400d01f13aaffd9387fe2b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-11 03:31:03
    Evidence reason
    unavailable
  24. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-11 03:31:03.000000
    Evidence SHA-256
    ef936acf985bfbf4d66675b141f6eb734629adf0c0a7643826b2be7ba846fde7
    Evidence timestamp as recorded
    2026-10-11 03:31:03
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  25. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-09 03:44:17.000000
    Evidence SHA-256
    e3d033a4834331026868e38810f2d82b4aed56a7f32c305b6eaa5517ced95ffb
    Evidence timestamp as recorded
    2026-10-09 03:44:17
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  26. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-09 03:44:17.000000
    Evidence SHA-256
    f8b155e6a120457fe2be87d3f131df1fd7b098487f20f1c21cfab789c665e0e0
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-09 03:44:17
    Evidence reason
    unavailable
  27. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 04:08:18.000000
    Evidence SHA-256
    42fd7d71f2d3124e08ef19511db065fec71a44a5b9eee25e64f8e006fa52457e
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-07 04:08:18
    Evidence reason
    transient_502
  28. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-07 04:08:18.000000
    Evidence SHA-256
    78ff8bc91e40fa3749c843aa0a3dca2fa048d45c63faeb613b3a17a263dd8a15
    Evidence timestamp as recorded
    2026-10-07 04:08:18
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  29. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 03:52:41.000000
    Evidence SHA-256
    0594256142138ba67a8569552226b68bf6d257c1691ec9ea81c95ac7dd75ff84
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-03 03:52:41
    Evidence reason
    transient_502
  30. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-03 03:52:41.000000
    Evidence SHA-256
    4dda685959b03a3fda2a69a8e2c2ccd1678b5687aac030ef7a2c35a937abc975
    Evidence timestamp as recorded
    2026-10-03 03:52:41
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  31. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 03:54:46.000000
    Evidence SHA-256
    88917d85fcec46034d4086a17efd5a9b17189527e998d40229a199ffc9e0925f
    Evidence timestamp as recorded
    2026-10-01 03:54:46
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  32. http_observationunknown
    Observation source
    http_observation
    Cause
    origin_unreachable
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    502
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    http_5xx
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-01 03:54:46.000000
    Evidence SHA-256
    c890049dc934407ce5e47e96571b85a3b1f60e0c65a2a2adf9a44f70a0a4d04f
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-01 03:54:46
    Evidence reason
    transient_502

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    duplicate-disabled-170698.invalid detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 45
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • Content Observed Unavailable
    Monitoring recorded an unavailable response; the cause was not independently established.
Publication & AvailabilityDestroyList Published · Content Observed Unavailable · Time to First Unavailability Recorded: 3 of 3
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 98

Recorded activity

2 entries
  1. URLScan

    Page captured

    View source
  2. Added to PhishDestroy

    duplicate-disabled-170698.invalid

    View source
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

duplicate-disabled-170698.invalid

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Server error
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including duplicate-disabled-170698.invalid)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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 →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/duplicate-disabled-170698.invalid"
  title="PhishDestroy threat report for duplicate-disabled-170698.invalid"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>