Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 15. 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-420660.invalid favicon

duplicate-disabled-420660.invalid

In short

duplicate-disabled-420660.invalid is a phishing page detected by PhishDestroy on 2026-08-09.

Resolved IP
Türkiye78.135.82.192HostLAB Bilisim Teknolojileri
Registered
Jun 11, 2026
First observed
Aug 10, 2026
PhishDestroy assessment Critical
95/100
Evidence score
Availability Content unavailable Content was unavailable in the latest observation Observed HTTP probe
VirusTotal detections: 15/89
VirusTotal
engine detections ·
Page captures
open gallery
Domain age
Aug 10, 2026
X Telegram API

Analysis

Domain summary

duplicate-disabled-420660.invalid is a phishing page detected by PhishDestroy on 2026-08-09. Risk: critical (95/100). Status: Content unavailable. Hosting: HostLAB Bilisim Teknolojileri A.S. VirusTotal: 15/89 engines flag it. Do not enter credentials or connect a wallet.

Critical
Status
Content unavailable
VirusTotal
15 / 89
Hosting
Türkiye78.135.82.192HostLAB Bilisim Teknolojileri
Registered
Jun 11, 2026
Page captures
1

PhishDestroy threat report

Overview

duplicate-disabled-420660.invalid is a domain on the PhishDestroy blocklist. It has not yet been assigned a specific scheme type, and no impersonated brand has been identified. PhishDestroy first saw it on 2026-08-10. The site has been offline since 2026-09-25 and was still unreachable at the last check on 2026-10-19.

How the scam works

The served page carried only the title "403 Forbidden", so its content gives no sign of what it was meant to imitate. That title is a server access-denied message, while the domain sits on our blocklist as suspicious. Fifteen security vendors independently flagged the domain, which suggests it was associated with harmful activity rather than being an ordinary broken site. On domains like this, the main risk is a page that asks for wallet connections, seed phrases or login credentials. No specific scheme has been confirmed for this one.

Evidence

On 2026-09-14, VirusTotal showed detections from 15 of 89 engines. That is a meaningful minority for a site with no visible content. The flagging vendors include Kaspersky, BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, alphaMountain.ai and the Vietnamese anti-scam project Chong Lua Dao. Detection by that many unrelated vendors, combined with PhishDestroy's own listing, is why the domain is treated as unsafe.

Infrastructure

The domain resolved to 78.135.82.192 on the HostLAB Bilisim Teknolojileri A.S. network in Turkey. It used a free, automatically issued Let's Encrypt certificate, so the padlock in the browser said nothing about whether the site was trustworthy. The domain stayed online for roughly six weeks after PhishDestroy first saw it, then went dark on 2026-09-25.

What to do

If you visited this domain and entered a password, change it and turn on two-factor authentication for that account. If you connected a crypto wallet or approved a transaction there, review and revoke any token approvals you do not recognize. If you typed in a seed phrase, move your funds to a new wallet immediately. Defenders should block the domain and its IP at DNS and proxy level. They should also search logs for past connections and report any related domains that appear on the same hosting.

Source evidenceVirusTotal 15 / 89 7 sources

VirusTotal

15 / 89 engine detections

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

3d31534b-533c-4f6e-81af-a93895ff3992

Final URL

https://www.tetherusdtistanbul.com.websitedukkani.com.tr/

HTTP response

403

Navigation history

  • URL
    https://www.tetherusdtistanbul.com.websitedukkani.com.tr/
    Status
    403

DOM structure hash

0a226e7ff0226df9c1b312239c3a21c005ded97c86cc005e8bbdb5decc778a66

Document hash

7271dd5c11fb9a1052a5e91a09afbe7d148fd3388dc51c338df62a0a16f06739

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    www.tetherusdtistanbul.com.websitedukkani.com.tr
    Type
    A
    Value
    78.135.82.192

DNSSEC valid

No

IP address

78.135.82.192

Registration record

Registered
Expires
Original source fields · JSON
Uuid
3d31534b-533c-4f6e-81af-a93895ff3992
Final url
https://www.tetherusdtistanbul.com.websitedukkani.com.tr/
Status
403
History
[
    {
        "url": "https://www.tetherusdtistanbul.com.websitedukkani.com.tr/",
        "status": 403
    }
]
DOM structure hash
0a226e7ff0226df9c1b312239c3a21c005ded97c86cc005e8bbdb5decc778a66
Document hash
7271dd5c11fb9a1052a5e91a09afbe7d148fd3388dc51c338df62a0a16f06739
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "www.tetherusdtistanbul.com.websitedukkani.com.tr",
        "type": "A",
        "value": "78.135.82.192"
    }
]
Dnssec valid
false
Ip
78.135.82.192
Registration record
{
    "created": "2026-06-11T00:00:00Z",
    "expires": "2027-06-10T00:00:00Z"
}

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-tetherusdtistanbul-com-websitedukkani-com-tr"}
stored_record
{"gs_trust_score":0,"gs_status":"not_found","gs_signals":null,"gs_url":"https://gridinsoft.com/online-virus-scanner/url/www-tetherusdtistanbul-com-websitedukkani-com-tr","gs_rating":null,"gs_reviews":0}

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
duplicate-disabled-420660.invalid — Suspicious Domain
ai_description
duplicate-disabled-420660.invalid is a suspicious domain on the PhishDestroy blocklist, flagged by 15 security vendors; crypto users should avoid it.
ai_generated_at
2026-10-19T10:54:31Z
ai_generated_by
threat-anthropic
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Questions about duplicate-disabled-420660.invalid

Is duplicate-disabled-420660.invalid legit?

No. PhishDestroy classifies duplicate-disabled-420660.invalid as a phishing page (risk: critical, 95/100); it was first detected on 2026-08-09. VirusTotal: 15/89 engines flag it. Treat the site as unsafe.

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

No. Do not connect a wallet, sign messages or approve tokens on duplicate-disabled-420660.invalid. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

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

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 1 capture

All capture links and hashes (1)
  • Cloudflare Radar · 2026-08-11 01:06 UTC · Source report
    SHA-256: 28fa085914a8eac5b91d635b1475d50ebd3886d62a2cad2787a06d991cd27055 · 33477 bytes
duplicate-disabled-420660.invalid: caution — 15/89 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card duplicate-disabled-420660.invalid: caution — 15/89 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v c76e80e78c51

Domain details

Domain
IP Reputation Türkiye78.135.82.192 abuse score 10/100 5 reports Port ScanBrute-Force checked Sep 10, 2026 last reported
RegistrationCreated Jun 11, 2026 (139d) — Expires Jun 10, 2027
Time to First Unavailability 46 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 DetectedAug 10, 2026
Favicon Hash
Observed page title
403 Forbidden
TLS Certificate
Issued by Let's Encrypt · stored validity ends in 54 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Türkiye78.135.82.192
Network ASN
AS207326
Organization
HostLAB Bilisim Teknolojileri
Observed location
TürkiyeIstanbul, TR
Server header
LiteSpeed

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-07-08 13:36:09
Valid until
2026-10-06 13:36:08
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-08-11 07:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdd22e9f91aec5ef83c7888c1a07df0177196a5d2640e828e3178e26092b33db6
Certificate names · 2 SANs
  • tetherusdtistanbul.com
  • tetherusdtistanbul.com.websitedukkani.com.tr

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

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

VirusTotal Analysis

15 / 89 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
Chong Lua Dao
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
PhishFort
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

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

100
Good
Performance
FCP
0.78 s
First Contentful Paint
LCP
0.78 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.62 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.

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 observations26

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-10-27 03:25:48.000000
    Evidence SHA-256
    426dde6090b09571a9454b8f8558b1b1c5032b548cb57138511d13afc985d2de
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 03:25:48
    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-10-27 03:25:48.000000
    Evidence SHA-256
    426dde6090b09571a9454b8f8558b1b1c5032b548cb57138511d13afc985d2de
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 03:25:48
    Evidence reason
    unavailable
  3. 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:21:54.000000
    Evidence SHA-256
    2121c89c47deb378f2812c3ca503d603505e900c0370cec5fe3e5c5347b67eda
    Evidence timestamp as recorded
    2026-10-25 03:21:54
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  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-25 03:21:54.000000
    Evidence SHA-256
    e5da0a61aa05c350a9db3084c52e35459bd469eee296af8c4f1858954f92bb60
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 03:21:54
    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-23 03:26:28.000000
    Evidence SHA-256
    0bf7124759a4329d160a911b04081119750c19e15c7341d5acbf72e6bc7a8a3e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 03:26:28
    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-23 03:26:28.000000
    Evidence SHA-256
    e27046bffbf7536c1e86f237fe654a109571ad4fc2fffacc4cd7f983e29a2b36
    Evidence timestamp as recorded
    2026-10-23 03:26:28
    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-21 03:16:25.000000
    Evidence SHA-256
    00149897b1a2d608be1b6d9a00fa5ba7f799341027b78c42cbb725d7835d4552
    Evidence timestamp as recorded
    2026-10-21 03:16:25
    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-21 03:16:25.000000
    Evidence SHA-256
    77e3e67715140f9dd9cd6442f2814a4985afb88d86ce02bccee1069bed55aeaa
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 03:16:25
    Evidence reason
    unavailable
  9. 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:07.000000
    Evidence SHA-256
    3f62ed3666a65d0ddd518ee97be88bd79c76d6556d120c2c33a92df87edd687c
    Evidence timestamp as recorded
    2026-10-19 03:16:07
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  10. 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:07.000000
    Evidence SHA-256
    7774ebdbfcf0f3a94528cc8f34a0b59b1f92989566b0bb54618188c32524188c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 03:16:07
    Evidence reason
    unavailable
  11. 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:27.000000
    Evidence SHA-256
    3e85bfd75738d92c1606054bf36178c910bbc9440899cec7b524516746ba5799
    Evidence timestamp as recorded
    2026-10-17 03:15:27
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  12. 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:27.000000
    Evidence SHA-256
    85e7ca2b926bed3a5ec093674525d8eb02e2db87d23b73f7c2829da07c8b2a2a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-17 03:15:27
    Evidence reason
    unavailable
  13. 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:20.000000
    Evidence SHA-256
    3c8de0f9164679712cc8e37ae8b7ddc19350fe45c9a5a34422a6abd54e5e7532
    Evidence timestamp as recorded
    2026-10-15 03:16:20
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  14. 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:20.000000
    Evidence SHA-256
    8633113c766893bf0dc57f8f83342bbabea72491bdee4a33b5d7980401c6192d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-15 03:16:20
    Evidence reason
    unavailable
  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-13 03:31:32.000000
    Evidence SHA-256
    38489aace463f2219707f4b3daa538013cb6c61b8cf00ac7bf972c5981086fb7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-13 03:31:32
    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-13 03:31:32.000000
    Evidence SHA-256
    c73ddadc3a7fbaca22e51f9c3d9b9913824d3e38b28e25b595df1055a8707bb6
    Evidence timestamp as recorded
    2026-10-13 03:31:32
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  17. 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:30:50.000000
    Evidence SHA-256
    16cc39fd876f96ef1ad72d670eae5aada28f2a4bea699568486feb2ba724b382
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-11 03:30:50
    Evidence reason
    unavailable
  18. 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:30:50.000000
    Evidence SHA-256
    8b777754705d8c0c60e0806dbbf62bc41015434b68046f2254af1054319df3f5
    Evidence timestamp as recorded
    2026-10-11 03:30:50
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  19. 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:05.000000
    Evidence SHA-256
    13c01b88987e48a0d13c2a0d608344b1efea5f810d5c7fdc5265715c3f8ce1a3
    Evidence timestamp as recorded
    2026-10-09 03:44:05
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  20. 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:05.000000
    Evidence SHA-256
    b9715ba78bbac5bface5546857f5183a45b597e0a707a967e3dfe935c5da87bc
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-09 03:44:05
    Evidence reason
    unavailable
  21. 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:07:58.000000
    Evidence SHA-256
    26f78ff6d72d564df1d96e5c7fada0a2f90993b5aa8abab282be359e6718ac67
    Evidence timestamp as recorded
    2026-10-07 04:07:58
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  22. 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:07:58.000000
    Evidence SHA-256
    3133f445b341681f705bf37073bb0e2a475ea6f0afb0c61a9f2c5aa54c246587
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-07 04:07:58
    Evidence reason
    transient_502
  23. 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:25.000000
    Evidence SHA-256
    a451d6ba1ab8535a9c84eedfd2c3e9e88762782ab010961d92dc9b162bf5e2cd
    Evidence timestamp as recorded
    2026-10-03 03:52:25
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  24. 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:25.000000
    Evidence SHA-256
    c462ed37e6f9ee6309744633c5ddb20ef7065521af455427f65e536f26496068
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-03 03:52:25
    Evidence reason
    transient_502
  25. 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:33.000000
    Evidence SHA-256
    9261f5035e5b2b36254cb4d49af90d8dcf6581a3eaa20571ee3db96cefd8d2b2
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-01 03:54:33
    Evidence reason
    transient_502
  26. 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:33.000000
    Evidence SHA-256
    a2c3731a566cfbf3a2b925cb5ca1bb29bd759ffcc967d3b01ebfd984437ab84b
    Evidence timestamp as recorded
    2026-10-01 03:54:33
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 9. 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-420660.invalid detected and queued for full analysis
Threat Intelligence ChecksCloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable Recorded: 5 of 5
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 15/89
  • Forensic Evidence Collected
    Stored evidence from 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: 1106

Recorded activity

2 entries
  1. VirusTotal

    15/89 engine detections

    View source
  2. Added to PhishDestroy

    duplicate-disabled-420660.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-420660.invalid

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

2 evidence signal groups linked Content unavailable
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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

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 →.

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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-420660.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.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

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-420660.invalid"
  title="PhishDestroy threat report for duplicate-disabled-420660.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>