Highscore 44 · flagged Thursday, October 15, 2026

protocolsecure.site

Appeared in the .site zone on Thursday, October 15, 2026; by the end of that day the census found redirects elsewhere. 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

lure words (login, verify, secure…)
matched: secure
+6
brand in page title, not in the name
matched: google
+20
form on a brand-styled page
matched: has_form
+18
Registrar
HOSTINGER operations, UAB
Nameserver provider
Nameservers
byte.dns-parking.com, pixel.dns-parking.com
First-day state
redirects elsewhere
HTTP status
200
Page title
ProtocolSecure - Web Güvenlik Denetim Aracı
Has a form
yes
Brand echoed
—

Model opinions

First passsuspiciousconfidence 72%· claude-haiku-4-5

protocolsecure.site redirects to protocolsecure.net using DNS-parking nameservers; the destination presents a legitimate-looking security audit tool in Turkish with a functional form, but the redirect structure (different domain to nearly-identical .net), use of parking infrastructure, and scorer detection of 'brand-in-title-not-name' (Google mentioned in page but not in domain name) suggest potential deception. However, no specific brand impersonation is evident — ProtocolSecure appears to be i

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 Thursday, October 15, 2026

Screenshot of protocolsecure.site taken by the zone census on 2026-10-15

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