On 24 July 2026 the domain www.elitebookings.pro was identified as a high‑risk generic phishing site. The authoritative WHOIS record shows registration through NameCheap, Inc. and the domain is served by the nameservers dns1.registrar-servers.com and dns2.registrar-servers.com. DNS resolution points to the IPv4 address 66.33.60.67, which belongs to Amazon.com, Inc. (AS16509) and is geolocated in the United States. The web server presents an HTTPS certificate issued by Let’s Encrypt (R12), and the TLS handshake includes HTTP Strict Transport Security (HSTS). Service fingerprinting indicates the site is hosted on the Vercel platform.
An HTTP request to the root URL returns a 302 redirect, and the page title reported by the crawler is “CelebBooking – Celebrity Booking Platform”. VirusTotal analysis shows that one out of ninety‑five scanning engines flagged the domain, confirming malicious intent. The domain appears on a single external blocklist and is actively blocked by the PhishDestroy feed, demonstrating that at least some security vendors have incorporated it into their protective controls. The available intelligence confirms a phishing infrastructure but lacks public samples of the landing page content, credential‑stealing forms, or specific victim targeting details.
Consequently, the precise payload and credential‑harvesting mechanisms remain unknown. Defenders should add the IPv4 address 66.33.60.67 to firewall deny lists, enforce DNS filtering for www.elitebookings.pro, and monitor outbound TLS connections to the Vercel‑hosted service. Continuous re‑scanning of the domain on VirusTotal and inclusion in internal URL blocklists is recommended, as the single detection may evolve into additional vendor flags. Given the high‑risk classification, any email or web traffic referencing the “CelebBooking” brand should be treated as suspicious, and users should be warned not to submit personal information to the site.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-1632.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 16, 2025
DOM Analysisanalyzed Jul 21, 2026score 56/100
Submitted URLhttps://www.elitebookings.pro/
Favicon Hash
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:31:40 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-23 02:12:06 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
V
Vercel
PaaSCDN
Cloud platform for frontend deployment, optimized for Next.js.
H
HSTS
Security
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-1632.invalid· checked Mar 2, 2026
95
Good
Performance
FCP
0.91s
First Contentful Paint
LCP
1.22s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
242ms
Total Blocking Time
SI
2.64s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-25 01:31:10 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-1632.invalid detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 25, 2026
Time to First Unavailability
4827 hours elapsed from detection to the first unavailable observation.
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.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches5
Same favicon hash or the same page title as this host.
(US)
