Skip to security report
refund-bookingid.netlify.app favicon
Domain security and threat intelligence

refund-bookingid.netlify.app

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

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.

Page title: “Cancellation & Payment Details - Booking.com”

More about the sources
Recorded security signals

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.

VirusTotal detections: 18/92 Stored blocklist matches: 1
Resolved IP
Germany35.157.26.135AWS EC2 (eu-central-1) · CDN
First seen by PhishDestroy
2026-11-21
Cloudflare Radar
Page captures
open gallery
2026-11-21 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

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.

Critical
Status
Last known active
VirusTotal
18 / 92
Blocklist matches
1 external + PhishDestroy list
Hosting
Germany35.157.26.135AWS EC2 (eu-central-1) · CDN
Page captures
7

Cloudflare Radar capture · 2026-11-21 17:47 UTC · SHA-256 811ddea5…8c4d224

PhishDestroy analysis, reviewed version

Booking refund cancellation form

The mobile-formatted page opens with a dark blue header showing the brand name "Booking.com" alongside a menu icon. Below the header, navigation tabs allow switching between "Stays", "Flights", "Flight + Hotel", and "Car rentals". The central content area displays a headline reading "Cancellation Details: Stays" followed by three input fields labeled "Enter Hotel Name / Accommodation", "Stay Dates (Check-in - Check-out)", and "Number of Rooms & Guests to Cancel". A checkbox asks users to confirm "I have read and agree to request a refund", positioned just above a grey action button reading "Request Refund". Further down, a green security badge displays "COMODO SECURED Point to Verify", while the footer mimics the corporate copyright notice "© 2026 Booking.com, a Booking Holdings company. All rights reserved.".

Security vendor telemetry

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 / 92 5 sources

VirusTotal

18 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields
Separate collector summary

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.

Source
VirusTotal
Result state
observed
Numerator
18
Denominator
92
Vendors
alphaMountain.ai, BitDefender, DNS8, ESET, Emsisoft, Fortinet, G-Data, Gridinsoft, Kaspersky, LevelBlue, Lionic, Netcraft, OpenPhish, SOCRadar, Sophos, URLQuery, VIPRE, Webroot
Observed at
2026-11-20 18:21:48
Checked at
2026-11-21 18:46:41
Fetched at
2026-11-21 17:46:41

URLScan

Malicious

SHA-256 d43db7c9…975d442

Open report
URLScanOriginal source recordObserved: 22 fields
Separate monitor record · 2026-11-22 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1ff31-13c8-744e-903b-41f539aefcd0
Score
100
Malicious
✓
Result at
2026-11-22T04:30:18Z
Enriched at
2026-11-22T09:13:13Z
Source timestamps
Urlscan result at: 2026-11-22 05:30:18; Urlscan enriched at: 2026-11-22 10:13:13

PhishDestroy DOM

10 / 100 · heuristic score · 3 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-11-21 19:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
10
Analyzed at
2026-11-21T19:20:08Z
Source timestamp
2026-11-21 20:20:08
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
refund-bookingid.netlify.app — Fake Booking cancellation
AI description
refund-bookingid.netlify.app mimics Booking with a fake cancellation portal, flagged by urlscan and 18 VirusTotal engines. Protect your accounts.
AI summary
Booking refund cancellation form The mobile-formatted page opens with a dark blue header showing the brand name "Booking.com" alongside a menu icon. Below the header, navigation tabs allow switching between "Stays", "Flights", "Flight + Hotel", and "Car rentals". The central content area displays a headline reading "Cancellation Details: Stays" followed by three input fields labeled "Enter Hotel Name / Accommodation", "Stay Dates (Check-in - Check-out)", and "Number of Rooms & Guests to Cancel". A checkbox asks users to confirm "I have read and agree to request a refund", positioned just above a grey action button reading "Request Refund". Further down, a green security badge displays "COMODO SECURED Point to Verify", while the footer mimics the corporate copyright notice "© 2026 Booking.com, a Booking Holdings company. All rights reserved.". Security vendor telemetry 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.
AI generated by
threat-v10-gemini
AI generated at
2026-11-21T18:24:31Z
Revision
8e7630a502709dd28af11cf72670108d2db7bcf1537ea7d5e10d3975782ae124
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

SPF lookups
0

CAA records

Count
3
Domain
netlify.app
Allowed issuers
  • digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226
  • amazon.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Page title and metadata

Page title
Cancellation & Payment Details - Booking.com

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
13
Download
1
Response time, ms
40

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
28431
CO₂, grams
0.001
Cleaner than, %
49

DNS servers

Nameservers
  • IP address
    198.51.45.65
    Host
    dns4.p01.nsone.net
  • IP address
    198.51.44.1
    Host
    dns1.p01.nsone.net
  • IP address
    198.51.45.1
    Host
    dns2.p01.nsone.net
  • IP address
    198.51.44.65
    Host
    dns3.p01.nsone.net
DNS zone
netlify.app

Page quality

Layout shift (CLS)
0.001
SEO score
90
Speed Index, s
0.8
First Contentful Paint (FCP), s
0.8
Largest Contentful Paint (LCP), s
0.8
Total Blocking Time (TBT), ms
0
Performance score
100
Accessibility score
100
Best practices score
100

Location

IP address
2a05:d014:58f:6200::259
ASN
16509
Organization
Amazon.com, Inc.
City
Frankfurt am Main
Country
DE

TLS certificate

Subject alternative names
  • *.netlify.app
  • netlify.app
Key size, bits
256
Certificate chain
  • *.netlify.app
  • DigiCert Global G2 TLS RSA SHA256 2020 CA1
  • DigiCert Global Root G2
Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Serial
0CD5D0AFB0611B5BD9D692535C0CA7C4
SHA-256
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Subject
*.netlify.app
Valid until
Valid from

DNS records

A
  • 35.157.26.135
  • 63.176.8.218
AAAA
  • 2a05:d014:58f:6200::258
  • 2a05:d014:58f:6200::259

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a05:d014:58f:6200::259
IP version
6

Redirects

Redirect chain
  • https://refund-bookingid.netlify.app

Technology stack

Technologies
  • Netlify
  • HSTS
  • DigiCert

Page links

Internal link addresses
  • https://refund-bookingid.netlify.app/
Internal links
1

HTTP headers

Response headers
Server
Netlify
Content-Type
text/html; charset=UTF-8
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 3; Domain: netlify.app; Issuers: digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226, amazon.com
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Page title and metadata
Title: Cancellation & Payment Details - Booking.com
Trackers
Requests: 2
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 13; Download: 1; Response ms: 40
TLS connection
Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
Carbon
Bytes: 28431; Co2 grams: 0.001; Cleaner than: 49
DNS server
NS: (IP: 198.51.45.65; Host: dns4.p01.nsone.net), (IP: 198.51.44.1; Host: dns1.p01.nsone.net), (IP: 198.51.45.1; Host: dns2.p01.nsone.net), (IP: 198.51.44.65; Host: dns3.p01.nsone.net); Zone: netlify.app
Quality
Cls: 0.001; Seo: 90; Si s: 0.8; Fcp s: 0.8; Lcp s: 0.8; Tbt ms: 0; Performance: 100; Accessibility: 100; Best practices: 100
Location
IP: 2a05:d014:58f:6200::259; ASN: 16509; Org: Amazon.com, Inc.; City: Frankfurt am Main; Country: DE
SSL
San: *.netlify.app, netlify.app; Bits: 256; Chain: *.netlify.app, DigiCert Global G2 TLS RSA SHA256 2020 CA1, DigiCert Global Root G2; Issuer: DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1; Serial: 0CD5D0AFB0611B5BD9D692535C0CA7C4; SHA256: bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478; Subject: *.netlify.app; Valid to: 2027-03-19T23:59:59Z; Valid from: 2026-02-16T00:00:00Z
DNS records
A: 35.157.26.135, 63.176.8.218; Aaaa: 2a05:d014:58f:6200::258, 2a05:d014:58f:6200::259
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=31536000; includeSubDomains; preload; Message: Site is compatible with the HSTS preload list!; Compatible: ✓
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: max-age=31536000; includeSubDomains; preload; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 2a05:d014:58f:6200::259; Family: 6
Redirects
Chain: https://refund-bookingid.netlify.app
Tech stack
Technologies: Netlify, HSTS, DigiCert
Page links
Internal: https://refund-bookingid.netlify.app/; Internal count: 1
HTTP headers
Headers: Server: Netlify; Content type: text/html; charset=UTF-8; Strict transport security: max-age=31536000; includeSubDomains; preload
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Questions about refund-bookingid.netlify.app

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

Explore

Blocklist matches1 external + PhishDestroy list · PhishDestroy · PhishFeed 1
PhishDestroy PhishDestroy list View source
PhishFeed Listed View source

Last checked

Page captures (7)

All capture links and hashes (7)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Booking report ↗
IP Context Germany35.157.26.135 Netlify shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider netlify.app
Abuse contactabuse@netlify.com
Hosting abuse contact abuse@netlify.com Amazon.com, Inc. · AS16509
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-21
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
Amex Mastercard Visa
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
Germany35.157.26.135
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
AWS EC2 (eu-central-1)
Observed location
GermanyFrankfurt, 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 fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Certificate 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.

Latest Classified Outcome 2026-11-22 11:59 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-22 11:59 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:59 UTC last 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
Detected via Cloudflare Radar · Wappalyzer engine

VirusTotal Analysis

18 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
URLQuery
Kaspersky
LevelBlue
OpenPhish
Gridinsoft
BitDefender
alphaMountain.ai
PageSpeed (mobile): 100

Google PageSpeed Insights — mobile performance audit of refund-bookingid.netlify.app ·

100
Good
Performance
FCP
0.77 s
First Contentful Paint
LCP
0.77 s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.8 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data108
Open complete records

Captured network requests

Network requests: 3 SHA-256 hashes: 3 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-11-21 17:41 UTC.

Open this scan on URLScan 01a1ff31-13c8-744e-903b-41f539aefcd0 ↗

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Serving page content

    page content returned

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

  1. Current http probeLive content
    Observation source
    Current http probe
    Cause
    Content served
    Availability state
    Content live
    Content state
    Served at root
    DNS state
    stale
    Recorded HTTP status
    200
    Monitor confidence
    90
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 12:59:23.000000
    Evidence SHA-256
    76f9b479312cb93735b79cd52c27c0b7e1a919e605fa4d4f18661e2279d77a5c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-22 12:59:23
    Evidence reason
    Alive content
  2. Current state backfill
    Observation source
    Current state backfill
    Cause
    Http 2xx unclassified
    DNS state
    stale
    Recorded HTTP status
    200
    Monitor confidence
    40
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-21 18:40:30.000000
    Evidence SHA-256
    c36296b6eb1e9b609e557c40499091ac1952247e862c7e9f722d55f6bcc1008a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-21 18:40:30
  3. Http observation
    Observation source
    Http observation
    Cause
    Http 2xx unclassified
    Recorded HTTP status
    200
    Monitor confidence
    40
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-21 18:40:30.000000
    Evidence SHA-256
    c36296b6eb1e9b609e557c40499091ac1952247e862c7e9f722d55f6bcc1008a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-21 18:40:30

Threat Response Pipeline

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

Recorded events: 11. 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
  • Threat Ingested
    refund-bookingid.netlify.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Cloudflare Radar: Malicious · Automated brand label: Booking · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+3117 d 19 h
  3. Added to PhishDestroy+23 h 18 min
  1. Cloudflare Radar

    Phishing

    +6 min
  2. Added to PhishDestroy

    refund-bookingid.netlify.app

    same minute
  3. URLScan

    Page captured

    +23 h 18 min
  4. 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
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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

refund-bookingid.netlify.app

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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
  • 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)
  • 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

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.

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.

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/refund-bookingid.netlify.app"
  title="PhishDestroy threat report for refund-bookingid.netlify.app"
  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>