Highscore 55 · flagged Friday, October 30, 2026

booking-secure.link

Appeared in the .link zone on Friday, October 30, 2026; by the end of that day the census found empty page. Full domain report

Signals, not verdicts. A domain appears here because heuristics matched its name, its infrastructure or the page it served on its first day. Where a model has looked at it, that is shown as an opinion with a confidence, not as a finding. Nothing on this page says a site is malicious. Read the evidence and decide for yourself.

Own one of these names and think the listing is wrong? Tell us and a person will look.

What matched

brand in the name
matched: booking
+30
lure words (login, verify, secure…)
matched: secure
+26
brand name behind Cloudflare
matched: cloudflare.com
+6
Registrar
—
Nameserver provider
Nameservers
armando.ns.cloudflare.com, jean.ns.cloudflare.com
First-day state
empty page
HTTP status
404
Page title
404 Not Found
Has a form
no
Brand echoed
booking

Model opinions

Second opinionsuspicioustarget: Booking.comconfidence 60%· claude-opus-5-5

The name 'booking-secure' on a cheap .link TLD resembles Booking.com's real secure.booking.com host and matches common hotel-reservation phishing patterns. However, the root returns only a styled 404 with no form, links or brand content, so there is nothing yet to show deception (path-gated kits often 404 at root).

First passsuspiciousconfidence 45%· typesafe/jev-latest

typesafe first pass (gate 0.4): p=suspicious:0.54 abuse:0.28 unreachable:0.14 | impersonates=0.13 credential=0.03 parked=0.92 evidence=1.0 | target=booking:0.63

A model looked at the screenshot and page text and wrote what it thought. It can be wrong, and it is not a finding.

What the page looked like on Friday, October 30, 2026

Screenshot of booking-secure.link taken by the zone census on 2026-10-30

Same data as JSON: /api/zone/domain/booking-secure.link. This page is not indexed by search engines and does not link to the site it describes.