The site presents a fraudulent Booking cancellation and refund portal designed to capture guest details. Visitors who submitted information or entered credentials should immediately contact their bank and monitor their accounts.
Stored VirusTotal result: 18/92 engines flagged. Malicious: 17. Suspicious: 1. Analysis time (as stored): 2026-11-20 18:21 UTC. Retrieved (as stored): 2026-11-21 17:46 UTC. Listed by external blocklists: PhishFeed. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded refund-bookingid.netlify.app on 2026-11-21. Stored VirusTotal result: 18/92 engines flagged. Malicious: 17. Suspicious: 1. Analysis time (as stored): 2026-11-20 18:21 UTC. Retrieved (as stored): 2026-11-21 17:46 UTC. Listed by external blocklists: PhishFeed. Risk: critical (evidence score 100/100). Status: Last known active. Hosting: Amazon.com, Inc. Do not enter credentials or connect a wallet.
urlscan classified the page as malicious, VirusTotal showed 18 of 92 engines flagging it on 20 Nov 2026, and PhishFeed blocks it, with Kaspersky, ESET and BitDefender among them. PhishDestroy scores the evidence against it at 75/100 (critical), so the page is recognized as a malicious credential collection trap rather than an authentic travel support service. The domain still responded on 21 Nov 2026 at 18:40 UTC while hosting this fraudulent form on netlify.app.
Recommended precautions
Do not submit any reservation details, personal names, or financial cards into the form fields. Anyone who already entered sensitive personal or payment information should immediately contact their financial institution to secure their accounts against unauthorized charges.
Source evidenceVirusTotal 18 / 925 sources
SourceResultRecorded · UTCOpen
VirusTotal
18 / 92 engine detections
Analysis:
Open report VirusTotalOriginal source recordObserved: 14 fields
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Is refund-bookingid.netlify.app an official Booking page?
No, it is an independent phishing page hosted on netlify.app designed to mimic Booking.com. Authentic customer service operations reside exclusively on the official Booking domain rather than third-party hosting providers.
What happens if I submitted my Booking details on refund-bookingid.netlify.app?
Entering reservation details or personal data into the cancellation form exposes you to follow-up social engineering or fraudulent support calls. You should treat the submitted information as compromised and monitor your associated email and bank accounts.
Why is this domain flagged by security tools?
urlscan classified the page as malicious, VirusTotal showed 18 of 92 engines flagging it on 20 Nov 2026, and PhishFeed blocks it. PhishDestroy scores the evidence against it at 75/100 (critical).
DOM Analysisanalyzed 2026-11-21score 10/1003 brand signals
Submitted URLhttp://refund-bookingid.netlify.app/
Favicon Hash
Observed page title
Cancellation & Payment Details - Booking.com
Automated brand references
AmexMastercardVisa
TLS Certificate
Issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1· stored validity ends in 117 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
35.157.26.135
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
AWS EC2 (eu-central-1)
Observed location
Frankfurt, DE
Server header
Netlify
Edge-IP reputation is not attributed to this domain.
Nameservers 4
dns1.p01.nsone.net
dns2.p01.nsone.net
dns3.p01.nsone.net
dns4.p01.nsone.net
Location describes the IP network.
TLS certificate
Issuer
DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from
2026-02-16 00:00:00
Valid until
2027-03-19 23:59:59
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478Certificate names · 2 SANs
*.netlify.app
netlify.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: Stale
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-22 11:59 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:59 UTClast content: 2026-11-22 11:59 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 2 identified
N
Netlify
PaaSCDN
Netlify providers hosting and server-less backend services for web applications and static websites.
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-11-21 17:41 UTC.
Loads saved data; the suspicious site is not opened.
Captured network requests
#
Network request
HTTP method · status
Type
Uncompressed size
Response body SHA-256
Stored observation history2
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Availability monitor · Recorded state
Serving page content
page content returned
Domain monitor · First collection record
Reachable
All retained availability observations3
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.
Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
4 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+3117 d 19 h
Added to PhishDestroy+23 h 18 min
Cloudflare Radar
Phishing
+6 min
Added to PhishDestroy
refund-bookingid.netlify.app
same minute
URLScan
Page captured
+23 h 18 min
VirusTotal
18/92 engine detections
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
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches5
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
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. Secure your accounts and funds first, then report. 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.
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
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 refund-bookingid.netlify.app)
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)
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
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.