Highscore 55 · flagged Friday, November 6, 2026

amazom-servicecenter.top

Appeared in the .top zone on Friday, November 6, 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

one-letter brand typo
matched: amazom≈amazon
+28
lure words (login, verify, secure…)
matched: service
+26
TLD with a high abuse rate
matched: top
+8
free DNS provider
matched: dnsowl.com
+8
Registrar
—
Nameserver provider
Nameservers
ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com
First-day state
empty page
HTTP status
404
Page title
404 Not Found
Has a form
no
Brand echoed
amazon

Model opinions

Second opinionlooks like abusetarget: Amazonconfidence 80%· claude-opus-5-5

The name 'amazom-servicecenter.top' typosquats Amazon (m for n) and adds 'service center' support-lure wording, on a cheap .top TLD with free dnsowl DNS. It currently serves only a bare nginx 404 with no content or form, so it is a brand-squat staged for deception rather than active phishing.

First passlooks like abusetarget: amazonconfidence 86%· typesafe/jev-latest

typesafe first pass (gate 0.4): p=abuse:0.88 suspicious:0.12 phishing:0.00 | impersonates=0.66 credential=0.03 parked=0.95 evidence=1.0 | target=amazon:1.00

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, November 6, 2026

Screenshot of amazom-servicecenter.top taken by the zone census on 2026-11-06

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