VirusTotal
13 / 89 engine detections
Open reportduubaiiimuseumm.webflow.io is a phishing page detected by PhishDestroy on 2026-09-16. Risk: critical (89/100). Registrar: MarkMonitor. Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 13/89 engines flag it. Do not enter credentials or connect a wallet.
“404 - Page not found”
13 / 89 engine detections
Open reportMalicious
Open reportno community references
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
duubaiiimuseumm.webflow.io is a subdomain on Webflow's free site-builder space whose name is a padded, misspelled form of "Dubai museum," a spelling pattern often used to dodge filters or mimic a legitimate name. PhishDestroy first saw it on 2026-09-16 and added it to our blocklist. The site went dead on 2026-09-21 and was still serving nothing at its root when last checked on 2026-10-19. The page title reads "404 - Page not found," which shows the content has been removed, while the domain remains listed by us as suspicious.
No live page remains, so the exact lure cannot be confirmed. A throwaway subdomain with a deliberately mangled name, flagged by over a dozen security engines within a week of appearing, fits the profile of short-lived pages used to collect personal or payment details or to redirect visitors elsewhere. Anyone who reached it through a link promising tickets, bookings or offers tied to a Dubai attraction should treat whatever they entered there as potentially exposed.
On 2026-09-23, 13 of 89 VirusTotal engines flagged the domain, including ESET, BitDefender, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, CyRadar and LevelBlue. That is a meaningful spread of independent vendors for a site that lived only a few days, and it backs the decision to block it. Among public blocklists, only PhishDestroy lists it.
Because it sits on a Webflow subdomain, the operator needed no domain registration of their own, only a free account, which makes such pages fast to create and easy to abandon. Traffic resolves through Cloudflare, Inc. at 172.64.151.8, geolocated to Canada, the shared front-end that serves many Webflow sites. The roughly five-day lifespan between first sighting on 2026-09-16 and going offline on 2026-09-21 points to a disposable page rather than a lasting project.
If you entered a password on this site, change it wherever you reuse it and turn on two-factor authentication. If you submitted card or bank details, contact your bank to block the card and watch for unfamiliar charges. Be wary of follow-up emails or messages that reference a booking or purchase you made through it. Defenders should block the full subdomain, search mail and proxy logs for visits since 2026-09-16, and report similar Webflow subdomains with distorted brand or place names to Webflow for removal.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 1b7df0a5-0fbf-4fd0-8737-304776e6120d |
|---|---|
| Final url | https://duubaiiimuseumm.webflow.io/ |
| Status | 404 |
| History | [
{
"url": "https://duubaiiimuseumm.webflow.io/",
"status": 404
}
] |
| DOM structure hash | 4932075438459d054af6b75a0d6585b123ae775f36579c095159b2af33360488 |
| Document hash | 90c032f35272ba1a7aa93027ab635e6610d4f24cf9e53c0624d00f065d7c7e7d |
| Domain risks | [
"Phishing",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "duubaiiimuseumm.webflow.io",
"type": "A",
"value": "172.64.151.8"
},
{
"name": "duubaiiimuseumm.webflow.io",
"type": "A",
"value": "104.18.36.248"
},
{
"name": "duubaiiimuseumm.webflow.io",
"type": "AAAA",
"value": "2a06:98c1:3102::ac40:9708"
},
{
"name": "duubaiiimuseumm.webflow.io",
"type": "AAAA",
"value": "2a06:98c1:3105::6812:24f8"
}
] |
| Dnssec valid | false |
| Ip | 172.64.151.8 |
| Verdict | {
"tags": [
"phishing"
],
"malicious": true,
"categories": [
"phishing"
]
} |
| Registration record | {
"registrar": "MarkMonitor Inc.",
"created": "2013-05-08T02:20:57Z",
"updated": "2026-08-12T04:04:30Z",
"expires": "2028-05-08T02:20:57Z",
"nameservers": [
"lamar.ns.cloudflare.com",
"journey.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 47,
"malicious": 14,
"suspicious": 0,
"undetected": 31
} |
|---|---|
| Vendor labels | {
"ESET": "phishing",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Webroot": "malicious",
"Fortinet": "phishing",
"SOCRadar": "phishing",
"LevelBlue": "phishing",
"PhishFort": "malicious",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Registrar | MarkMonitor Inc. |
| Created | 2013-05-08T02:20:57Z |
| Expires | 2028-05-08T02:20:57Z |
| Updated | 2026-08-12T04:04:30Z |
| First seen | 2026-09-16T13:48:16Z |
| DNS records | [
{
"ttl": 300,
"type": "AAAA",
"value": "2a06:98c1:3105::6812:24f8"
},
{
"ttl": 300,
"type": "A",
"value": "104.18.36.248"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2a06:98c1:3102::ac40:9708"
},
{
"ttl": 300,
"type": "A",
"value": "172.64.151.8"
}
] |
| Dns at | 2026-10-13T09:45:32Z |
| Jarm | 27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6 |
| Certificate | {
"san": [
"webflow.io",
"*.webflow.io"
],
"issuer": "Google Trust Services / WE1",
"serial": "ac972ef95a18ab8f0e5a2917e958d6da",
"sha256": "5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7",
"subject": "webflow.io",
"valid_to": "2026-12-21T03:46:57Z",
"valid_from": "2026-09-22T02:47:08Z"
} |
| Registration record | {
"registrar": "MarkMonitor Inc.",
"registrar_iana_id": "292",
"registrar_url": "http://www.markmonitor.com",
"created": "2013-05-08T02:20:57Z",
"updated": "2025-02-25T20:53:31Z",
"expires": "2028-05-08T02:20:57Z",
"status": [
"clientDeleteProhibited",
"clientTransferProhibited",
"clientUpdateProhibited"
],
"nameservers": [
"journey.ns.cloudflare.com",
"lamar.ns.cloudflare.com"
],
"dnssec": "unsigned"
} |
No. PhishDestroy classifies duubaiiimuseumm.webflow.io as a phishing page (risk: critical, 89/100); it was first detected on 2026-09-16. VirusTotal: 13/89 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on duubaiiimuseumm.webflow.io. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
Edge-IP reputation is not attributed to this domain.
journey.ns.cloudflare.comlamar.ns.cloudflare.comLocation describes the IP network.
5302eb12d2c1ddc8020e4565aef253a59e28b4a9aede60f73e4fe6cb516fd2a7webflow.io*.webflow.ioSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Reachable→Unavailable
Reachable
No threat flag
View source13/89 engine detections
View sourceduubaiiimuseumm.webflow.io
View source1 community report
CategoryPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-16T13:33:34.710Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
duubaiiimuseumm.webflow.io
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
duubaiiimuseumm.webflow.io)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.