VirusTotal
14 / 89 engine detections
Open reportmaadame---tusssauds-duubai.webflow.io is a Google impersonation page detected by PhishDestroy on 2026-09-16. Risk: critical (92/100). Registrar: MarkMonitor. Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 14/89 engines flag it. Do not enter credentials or connect a wallet.
“404 - Page not found”
14 / 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
This was an impersonation phishing page built on a free Webflow subdomain. Its padded, misspelled name imitates Madame Tussauds Dubai, the wax museum attraction. PhishDestroy first saw it on 2026-09-16. The site went offline on 2026-09-22 and was still dead with no content at its root on 2026-10-19.
Fake attraction pages like this one usually copy the venue's branding and offer tickets, discounts or giveaways. They then collect card details, personal data or direct payments that never turn into a valid booking. The doubled and tripled letters in the hostname help it slip past casual readers who only skim a link in an ad, message or search result. The page title now reads "404 - Page not found," which reflects the removed content rather than the impersonation PhishDestroy classified.
On 2026-09-23, 14 of 89 VirusTotal engines flagged the address. This is a meaningful consensus for a short-lived page on a shared builder domain. Vendors behind the verdict include alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and LevelBlue. The domain is also listed on the PhishDestroy blocklist.
The operator did not register a domain at all. They used a webflow.io subdomain, which costs nothing and inherits the platform's reputation and valid HTTPS. Traffic resolved to Cloudflare, Inc. addresses located in Canada, which is standard for Webflow-hosted sites. The page went dark six days after PhishDestroy first saw it, a typical lifespan for throwaway builder pages.
If you paid for tickets or entered card details on this page, contact your bank to dispute the charge and request a replacement card. If you gave it your email, phone number or passport details, watch for follow-up scams that reuse them. Change any password you typed there and enable two-factor authentication on that account. Buy Madame Tussauds Dubai tickets only through the venue's official site or established resellers. Defenders should block the hostname and treat look-alike webflow.io subdomains carrying attraction brands as suspicious.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 4b466fe6-fb07-4172-96ac-d6dd8a4fca2c |
|---|---|
| Final url | https://maadame---tusssauds-duubai.webflow.io/ |
| Status | 404 |
| History | [
{
"url": "https://maadame---tusssauds-duubai.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": "maadame---tusssauds-duubai.webflow.io",
"type": "A",
"value": "104.18.36.248"
},
{
"name": "maadame---tusssauds-duubai.webflow.io",
"type": "A",
"value": "172.64.151.8"
},
{
"name": "maadame---tusssauds-duubai.webflow.io",
"type": "AAAA",
"value": "2a06:98c1:3102::ac40:9708"
},
{
"name": "maadame---tusssauds-duubai.webflow.io",
"type": "AAAA",
"value": "2a06:98c1:3105::6812:24f8"
}
] |
| Dnssec valid | false |
| Ip | 104.18.36.248 |
| 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": 46,
"malicious": 13,
"suspicious": 0,
"undetected": 33
} |
|---|---|
| Vendor labels | {
"ESET": "phishing",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Webroot": "malicious",
"Fortinet": "phishing",
"LevelBlue": "phishing",
"Seclookup": "malicious",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| 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-16T14:25:24Z |
| DNS records | [
{
"ttl": 300,
"type": "AAAA",
"value": "2a06:98c1:3102::ac40:9708"
},
{
"ttl": 300,
"type": "A",
"value": "172.64.151.8"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2a06:98c1:3105::6812:24f8"
},
{
"ttl": 300,
"type": "A",
"value": "104.18.36.248"
}
] |
| Dns at | 2026-10-16T15:47:43Z |
| 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 maadame---tusssauds-duubai.webflow.io as a Google impersonation page (risk: critical, 92/100); it was first detected on 2026-09-16. VirusTotal: 14/89 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on maadame---tusssauds-duubai.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.
a4ffdefa8d99689893e2aafdf9588b6f8f2f8ec47698ea534dbfa409dbbde19dwebflow.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 source14/89 engine detections
View sourcemaadame---tusssauds-duubai.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:34:13.746Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
maadame---tusssauds-duubai.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 ↗
maadame---tusssauds-duubai.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.