VirusTotal
1 / 89 engine detections
Open reporttussaudsdubai----madame.webflow.io is a Google impersonation page detected by PhishDestroy on 2026-09-16. Risk: high (61/100). Registrar: MarkMonitor. Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 1/89 engines flag it. Do not enter credentials or connect a wallet.
“404 - Page not found”
1 / 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 Webflow-hosted subdomain impersonates Madame Tussauds Dubai, the wax museum attraction. It aims at tourists and residents searching for the museum online. PhishDestroy first flagged it on 2026-09-16 and classified it as an impersonation phishing page. The site has been offline since 2026-09-22, and the root still served no content when last checked on 2026-10-19.
Attraction impersonation pages copy a venue's name and branding on a free site-builder address so they look like an official booking page. They usually push discounted or 'last-minute' tickets, then collect card details, names, phone numbers and email addresses through a checkout that leads nowhere. Victims lose the payment and expose card data that can be reused for further fraud. The repeated hyphens and the word order in this subdomain put the brand name up front, which can pass a quick glance on a phone screen. The page now returns the title '404 - Page not found', while our classification is impersonation phishing.
Independent detection is thin. On 2026-09-23, only LevelBlue among 89 VirusTotal engines flagged the address, and PhishDestroy is the only blocklist listing it. This low count reflects how briefly the page was up, about six days between our first sighting and its takedown, rather than any sign that it is safe.
The operator used a free Webflow subdomain instead of registering a domain, which costs nothing and avoids a registrar trail. Traffic resolves through Cloudflare, Inc. at 172.64.151.8, geolocated to Canada. The Google Trust Services certificate comes from the platform's shared setup, so the padlock says nothing about whether the page is legitimate.
If you paid or entered card details on this page, call your bank right away to block the card and dispute the charge, and watch your statements for small test transactions. If you shared an email address or phone number, expect follow-up 'booking confirmation' or refund messages and do not click their links. Buy Madame Tussauds Dubai tickets only through the attraction's official site or authorised resellers you reach yourself. Defenders should block this subdomain and similar brand-plus-hyphen patterns on webflow.io, and report any new variants to Webflow's abuse team.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | c3d8b204-904a-47d4-8e7b-c0a5604017aa |
|---|---|
| Final url | https://tussaudsdubai----madame.webflow.io/ |
| Status | 404 |
| History | [
{
"url": "https://tussaudsdubai----madame.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": "tussaudsdubai----madame.webflow.io",
"type": "A",
"value": "172.64.151.8"
},
{
"name": "tussaudsdubai----madame.webflow.io",
"type": "A",
"value": "104.18.36.248"
},
{
"name": "tussaudsdubai----madame.webflow.io",
"type": "AAAA",
"value": "2a06:98c1:3102::ac40:9708"
},
{
"name": "tussaudsdubai----madame.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": 46,
"malicious": 13,
"suspicious": 0,
"undetected": 33
} |
|---|---|
| Vendor labels | {
"ESET": "phishing",
"VIPRE": "malware",
"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-16T13:11:19Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "172.64.151.8"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2a06:98c1:3102::ac40:9708"
},
{
"ttl": 300,
"type": "A",
"value": "104.18.36.248"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2a06:98c1:3105::6812:24f8"
}
] |
| Dns at | 2026-10-16T14:47:12Z |
| 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 tussaudsdubai----madame.webflow.io as a Google impersonation page (risk: high, 61/100); it was first detected on 2026-09-16. VirusTotal: 1/89 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on tussaudsdubai----madame.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
14→1
Reachable→Unavailable
Reachable
No threat flag
View source1/89 engine detections
View sourcetussaudsdubai----madame.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-16T12:35:30.322Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
tussaudsdubai----madame.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 ↗
tussaudsdubai----madame.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.