Skip to security report
Analytics Dashboard
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-362793.invalid favicon

duplicate-disabled-362793.invalid

In short

PhishDestroy first recorded duplicate-disabled-362793.invalid on 2026-06-12. VirusTotal: 11/91 engines flag it.

“www.exploredubaibookings.webflow.io”

Review the evidence
Registrar
United StatesWebflow
Resolved IP
Canada172.64.151.8Cloudflare, Inc. · CDN
First observed
Jun 12, 2026
PhishDestroy assessment Critical
83/100
Evidence score
Availability Server error The latest stored response was inconclusive Observed HTTP probe
Risk signals
VirusTotal detections: 11/91
VirusTotal
11 / 91
engine detections
URLScan
Malicious
engine verdict · score 60
Page captures
2
open gallery
Jun 12, 2026 CDN
X Telegram API

Questions about duplicate-disabled-362793.invalid

Is duplicate-disabled-362793.invalid legit?

PhishDestroy rates duplicate-disabled-362793.invalid as critical risk (83/100) from the recorded evidence; it was first recorded on 2026-06-12. VirusTotal: 11/91 engines flag it. Treat the site as unsafe.

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

This report does not record which wallet requests duplicate-disabled-362793.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-362793.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 / 91 6 sources

VirusTotal

11 / 91 engine detections

Open report

URLScan

Malicious · engine verdict · score 60

Open report
URLScanOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Report ID

019ebd9f-8899-75b3-9b71-e0b78c2f19cf

Final URL

http://www.exploredubaibookings.webflow.io/

Redirects

  • To
    https://www.exploredubaibookings.webflow.io/
    From
    http://www.exploredubaibookings.webflow.io/
    Status
    307
  • To
    http://www.exploredubaibookings.webflow.io/
    From
    https://www.exploredubaibookings.webflow.io/
    Status
    307
  • To
    https://www.exploredubaibookings.webflow.io/
    From
    http://www.exploredubaibookings.webflow.io/
    Status
    307

Document hash

21ece3f4761e00274f27ff6f9c7dd25e5608879e7c92f7b4efe73af03a1f2e7c

JavaScript globals

  • assert
  • getRequiredElement
  • P
  • S
  • getRandomNum
  • getTimeStamp
  • Dimensions
  • Config$2
  • getGlobalConfig
  • setGlobalConfig
  • Config$1
  • Config
  • setMaxGapCoefficient
  • setMaxObstacleLength
  • Status
  • A11yStrings
  • RunnerClasses
  • RunnerSounds
  • RunnerEvents
  • updateCanvasScaling
  • getA11yString
  • vibrate
  • createCanvas
  • decodeBase64ToArrayBuffer
  • createAdjustedCollisionBox
  • drawCollisionBoxes
  • boxCompare
  • toggleHelpBox
  • diagnoseErrors
  • portalSignin
  • updateForDnsProbe
  • getMainFrameErrorCssClass
  • getMainFrameErrorIconCssClass
  • getSubFrameErrorIconCssClass
  • shouldShowSuggestionsSummaryList
  • getSuggestionsSummaryItemCssClass
  • reloadButtonClick
  • downloadButtonClick
  • detailsButtonClick
  • setAutoFetchState

Domain age, days

0

Registered domain age, days

280

Page requests

5

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
60
Malicious
Yes
Overall verdict
Score
0
Malicious
No
Original source fields · JSON
Uuid
019ebd9f-8899-75b3-9b71-e0b78c2f19cf
Final url
http://www.exploredubaibookings.webflow.io/
Redirects
[
    {
        "to": "https://www.exploredubaibookings.webflow.io/",
        "from": "http://www.exploredubaibookings.webflow.io/",
        "status": 307
    },
    {
        "to": "http://www.exploredubaibookings.webflow.io/",
        "from": "https://www.exploredubaibookings.webflow.io/",
        "status": 307
    },
    {
        "to": "https://www.exploredubaibookings.webflow.io/",
        "from": "http://www.exploredubaibookings.webflow.io/",
        "status": 307
    }
]
Document hash
21ece3f4761e00274f27ff6f9c7dd25e5608879e7c92f7b4efe73af03a1f2e7c
Globals
[
    "assert",
    "getRequiredElement",
    "P",
    "S",
    "getRandomNum",
    "getTimeStamp",
    "Dimensions",
    "Config$2",
    "getGlobalConfig",
    "setGlobalConfig",
    "Config$1",
    "Config",
    "setMaxGapCoefficient",
    "setMaxObstacleLength",
    "Status",
    "A11yStrings",
    "RunnerClasses",
    "RunnerSounds",
    "RunnerEvents",
    "updateCanvasScaling",
    "getA11yString",
    "vibrate",
    "createCanvas",
    "decodeBase64ToArrayBuffer",
    "createAdjustedCollisionBox",
    "drawCollisionBoxes",
    "boxCompare",
    "toggleHelpBox",
    "diagnoseErrors",
    "portalSignin",
    "updateForDnsProbe",
    "getMainFrameErrorCssClass",
    "getMainFrameErrorIconCssClass",
    "getSubFrameErrorIconCssClass",
    "shouldShowSuggestionsSummaryList",
    "getSuggestionsSummaryItemCssClass",
    "reloadButtonClick",
    "downloadButtonClick",
    "detailsButtonClick",
    "setAutoFetchState"
]
Domain age days
0
Apex age days
280
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 60,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
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
019ebd9f-8899-75b3-9b71-e0b78c2f19cf
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

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Report ID

9e4df7ae-81be-4eec-aa4d-a43efdb60bc4

Final URL

https://www.exploredubaibookings.webflow.io/

Navigation history

  • URL
    https://www.exploredubaibookings.webflow.io/
    Status
    0

DOM structure hash

f7a48cc844a2898cdb50aa55394e2633ea45e5ef13dc1aed1292ed349b65d815

Domain risk categories

  • Information Technology
  • Technology

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    www.exploredubaibookings.webflow.io
    Type
    A
    Value
    104.18.36.248
  • Name
    www.exploredubaibookings.webflow.io
    Type
    A
    Value
    172.64.151.8
  • Name
    www.exploredubaibookings.webflow.io
    Type
    AAAA
    Value
    2a06:98c1:3102::ac40:9708
  • Name
    www.exploredubaibookings.webflow.io
    Type
    AAAA
    Value
    2a06:98c1:3105::6812:24f8

DNSSEC valid

No

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • lamar.ns.cloudflare.com
  • journey.ns.cloudflare.com
Original source fields · JSON
Uuid
9e4df7ae-81be-4eec-aa4d-a43efdb60bc4
Final url
https://www.exploredubaibookings.webflow.io/
History
[
    {
        "url": "https://www.exploredubaibookings.webflow.io/",
        "status": 0
    }
]
DOM structure hash
f7a48cc844a2898cdb50aa55394e2633ea45e5ef13dc1aed1292ed349b65d815
Domain risks
[
    "Information Technology",
    "Technology"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "www.exploredubaibookings.webflow.io",
        "type": "A",
        "value": "104.18.36.248"
    },
    {
        "name": "www.exploredubaibookings.webflow.io",
        "type": "A",
        "value": "172.64.151.8"
    },
    {
        "name": "www.exploredubaibookings.webflow.io",
        "type": "AAAA",
        "value": "2a06:98c1:3102::ac40:9708"
    },
    {
        "name": "www.exploredubaibookings.webflow.io",
        "type": "AAAA",
        "value": "2a06:98c1:3105::6812:24f8"
    }
]
Dnssec valid
false
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2013-05-08T02:20:57Z",
    "updated": "2024-12-12T21:40:03Z",
    "expires": "2028-05-08T02:20:57Z",
    "nameservers": [
        "lamar.ns.cloudflare.com",
        "journey.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

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
Network Security Intelligence
SSL Certificate Invalid
SSL certificate is invalid or expired. Issuer:
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 2 captures

URLScan · 2026-06-12 1 / 2
SourceURLScan · 2026-06-12
Recorded
StateStored capture
Final URLhttp://www.exploredubaibookings.webflow.io/
Position1 / 2
Open capture Source Report Wayback Download
All capture links and hashes (2)
Observed page title
www.exploredubaibookings.webflow.io
duplicate-disabled-362793.invalid: caution — 11/91 VirusTotal engines. PhishDestroy risk score 83/100 (critical).
Social preview card duplicate-disabled-362793.invalid: caution — 11/91 VirusTotal engines. PhishDestroy risk score 83/100 (critical). v 2e32e674a6ed

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 60 report ↗
IP Context Canada172.64.151.8 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Webflow US(US)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for duplicate-disabled-362793.invalid →
RegistrationExpires May 8, 2028
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 DetectedJun 12, 2026
Submitted URLhttp://www.exploredubaibookings.webflow.io/
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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.64.151.8
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

viewdns.info · 172.64.151.8rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

11 / 91 security vendors flagged this domain
View on VT
ADMINUSLabs
alphaMountain.ai
BitDefender
CyRadar
ESET
Fortinet
G-Data
Kaspersky
Lionic
Sophos
Webroot

Captured network requests

Network requests: 5 SHA-256 hashes: 4 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 03:25 UTC.

Open this scan on URLScan 019ebd9f-8899-75b3-9b71-e0b78c2f19cf ↗

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:11:51.000000
    Evidence SHA-256
    ddc6e472fd769036cd843c49580202d5d50b108976a051f3adfae047d8d3b737
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:11:51
    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:11:51.000000
    Evidence SHA-256
    ddc6e472fd769036cd843c49580202d5d50b108976a051f3adfae047d8d3b737
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 03:11:51
    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:12:50.000000
    Evidence SHA-256
    befb7f243fa21df6ffb5174170498ace87a65bd2d737f768af33fa6a81bcca0e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 03:12:50
    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:12:50.000000
    Evidence SHA-256
    befb7f243fa21df6ffb5174170498ace87a65bd2d737f768af33fa6a81bcca0e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 03:12:50
    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:19:56.000000
    Evidence SHA-256
    5bf5e6cdf76ee2d0b9bba89a4ffd50de46dece1f9227a9eb61f88c0e9a79b249
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 03:19:56
    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:19:56.000000
    Evidence SHA-256
    eecb96210aa977f7cf1db3c9afa47ae13f97c40f7a062ee0de94f713206ec09f
    Evidence timestamp as recorded
    2026-10-29 03:19:56
    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:20:24.000000
    Evidence SHA-256
    780cc3c92afedbbc7097fb27d966d1a48eb149d0ce551d04c5c9b2bd7d28c8b0
    Evidence timestamp as recorded
    2026-10-27 03:20:24
    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:20:24.000000
    Evidence SHA-256
    bcbb4ee61bb075336af481927d1014b294e50118cf4e0e18cdc1b4fc02e7ebe0
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 03:20:24
    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-25 03:17:21.000000
    Evidence SHA-256
    22c7383a364fdd08c885b3d46062763407033e8b3681f19de7cd397afff91935
    Evidence timestamp as recorded
    2026-10-25 03:17:21
    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-25 03:17:21.000000
    Evidence SHA-256
    fe2439044763b32cb699e27493bd5afdb0b6a968c7ee1ec7ecf527fa0a76220f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 03:17:21
    Evidence reason
    unavailable
  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:21:12.000000
    Evidence SHA-256
    8a62a44d7c6731a6f5e72383a6d8c03dc3745443f934dcacf2efd48c12937c04
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 03:21:12
    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:21:12.000000
    Evidence SHA-256
    a6db326ffca665747a85a2734af48957669090bfd5b6c5b90c35db1f1be1e34a
    Evidence timestamp as recorded
    2026-10-23 03:21:12
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  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-21 03:12:42.000000
    Evidence SHA-256
    2c40d27b849a3f9adc7fd71dcbc81013ab011e2b5cdafaf6b2a0b9f3360f315f
    Evidence timestamp as recorded
    2026-10-21 03:12:42
    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-21 03:12:42.000000
    Evidence SHA-256
    3ee910186c7b7caf057178b570ec2549ef8011e341aade188e8188176f5eff2e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-21 03:12:42
    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-19 03:12:17.000000
    Evidence SHA-256
    4d990cd6c6c134238586a351b6ffc22955b282ba92ad12dcbd438c7bab991864
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-19 03:12: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:12:17.000000
    Evidence SHA-256
    9bd2e560fbc11cc0737a373389aa787e0fcc5cd731eb9a347fd10288d6509817
    Evidence timestamp as recorded
    2026-10-19 03:12: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:11:25.000000
    Evidence SHA-256
    4c93cf2eb77aa4f7ded10eab825751a5756e5f0231d83b91e01aed585582f632
    Evidence timestamp as recorded
    2026-10-17 03:11:25
    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:11:25.000000
    Evidence SHA-256
    bed8ae90def7f9402f307e9b27428b86f701b252d67bfded7d126c63d062d77a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-17 03:11:25
    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:11:34.000000
    Evidence SHA-256
    37e375783c345f8eb2ed7a012dfce113a2047d3b30177e03706d29f9b73b1e16
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-15 03:11:34
    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:11:34.000000
    Evidence SHA-256
    f1d82c6fe42e330a1356b365d7a8ceb249797b2d88bad82dbb1c51bd500ff668
    Evidence timestamp as recorded
    2026-10-15 03:11:34
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  21. 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:14:08.000000
    Evidence SHA-256
    a468f45b69133db9ff3156712d1f8d3f7d802fb4a601667604b69081f662735f
    Evidence timestamp as recorded
    2026-10-13 03:14:08
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  22. 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:14:08.000000
    Evidence SHA-256
    d6e2567b4fef8de0dc9eaadb2a70277e272c84febf793f18c4d04e01a43705c3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-13 03:14:08
    Evidence reason
    unavailable
  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:12:55.000000
    Evidence SHA-256
    24eb051a970a804845def5b54db4e0ba53820285af92997b791c60cf2cf9abcb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-11 03:12:55
    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:12:55.000000
    Evidence SHA-256
    3c88d1ca338111426d0c702eb187bdea581ff5b036f01491e64a1333b9d1afb2
    Evidence timestamp as recorded
    2026-10-11 03:12:55
    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:22:37.000000
    Evidence SHA-256
    5367efa05a87d9e82de585adb99c3ddff8080cd2fd2e975336aa38cd573ea355
    Evidence timestamp as recorded
    2026-10-09 03:22:37
    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:22:37.000000
    Evidence SHA-256
    58c46a62699be63486d819e8e0437e8b5c1cad7c3e2c9b493365eac1c2cbea3f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-09 03:22:37
    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 03:38:59.000000
    Evidence SHA-256
    291cbdfd842c1649c229eabe93bd31fd3187b0d2f168850894e0d33ef682788d
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-07 03:38:59
    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 03:38:59.000000
    Evidence SHA-256
    76900778387f0ca0f8e3ba961bde8d21b755326a1d93e403c78a9459f7d3bf82
    Evidence timestamp as recorded
    2026-10-07 03:38:59
    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:32:45.000000
    Evidence SHA-256
    ba8161891af809909758dadce793e7d90d15f9758e7f477fef3cec7743a7e2af
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-03 03:32:45
    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:32:45.000000
    Evidence SHA-256
    ecf3b57e069cf80aba6a8951d86ad89f3f7701366086c0c7a05d0803079016fc
    Evidence timestamp as recorded
    2026-10-03 03:32:45
    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:34:48.000000
    Evidence SHA-256
    a4379715895ab1c648e883fc5ed4ed7467c5811992c46d2375d2c96f93933602
    Evidence timestamp as recorded
    2026-10-01 03:34:48
    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:34:48.000000
    Evidence SHA-256
    a5a6db3f4ff501bd1e03ff48a53a67113c489817539127f1bfa97d181dc79dce
    HTTP probe value as recorded
    502
    Evidence timestamp as recorded
    2026-10-01 03:34:48
    Evidence reason
    transient_502

Threat Response Pipeline

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

Recorded events: 8. 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-362793.invalid detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Forensic Evidence Collected Recorded: 4 of 4
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 60
  • 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.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
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: 1110

Recorded activity

2 entries
  1. Added to PhishDestroy

    duplicate-disabled-362793.invalid

    View source
  2. URLScan

    Malicious · engine verdict · score 60

    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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

duplicate-disabled-362793.invalid

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 11 det. ChainPatrol URLQuery SSL Labs CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

Request a correction or appeal How PhishDestroy works
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-362793.invalid"
  title="PhishDestroy threat report for duplicate-disabled-362793.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>