incident57.com

Valid HTTPS 16.5 years Updated
Anchor100 · incident57.com
Report ID: #3A9310F1 Verified
95
Very Safe
Verdict at a glance
IP Address104.21.41.60
Server LocationUnknown
RegistrarCloudflare, Inc.
Domain Age16.5 years

Open inspection of incident57.com

This page summarises the technical signals collected for incident57.com: server location, HTTPS status, registrar, domain age and DNS configuration.

IP Address · Server Location

104.21.41.60
Unknown

SSL Certificate

Valid HTTPS
WE1
Valid Until: 2026-08-23

Registrar

Cloudflare, Inc.
Registered On: 2009-11-30
16.5 years

Very Safe

95/100
Verdict at a glance

Snapshot

Snapshot of incident57.com: 16.5 years old, hosted in Unknown, ISP Unknown, HTTPS OK.

Lifespan

Counting from registration day, incident57.com has been around for approximately 16.5 years through Cloudflare, Inc. — within the "mature" maturity bracket of our scoring model.

Connection security

We performed a TLS handshake against incident57.com and got: OK. Combined with the registrar (Cloudflare, Inc.) and country (Unknown), this gives a baseline security view.

Network footprint

From a network perspective, incident57.com is hosted in Unknown through Unknown. This affects latency, applicable law and abuse-handling channels.

Reputation signals

Public infrastructure alone cannot prove a site is safe — it can only show whether it follows industry baselines (HTTPS, mature registration, traceable WHOIS). For trust beyond that, cross-check user reviews and your own communication with the operator.

In one sentence

incident57.com currently ranks very_safe with a score of 95/100, based purely on public infrastructure facts.

What looks good

  • Certificate validity window is current
  • Reachable on standard ports
  • Certificate issued by a recognised CA
  • No DNS hijack indicators in current records

What to watch

  • Uses generic shared hosting (cannot identify operator from IP)
  • TXT records expose minimal trust hints
  • TLS configuration accepts older cipher suites

Frequently Asked Questions

How often is incident57.com re-checked?
By default the report is refreshed every 30 days, plus on every manual re-check from the dashboard.
Is the score enough to decide?
A high score is necessary but not sufficient. Always pair the report with a content-level sanity check before transacting.
What ISP serves incident57.com?
The current network announcement comes from Unknown, with the IP geo-located in Unknown.
Where do I file a complaint about incident57.com?
You can file a takedown notice with the registrar (Cloudflare, Inc.) or the hosting ISP (Unknown). Each maintains a public abuse channel.
Does incident57.com have IPv6?
Our DNS lookup returns AAAA-record presence as part of the report. If absent, incident57.com is currently IPv4-only.

This report is generated automatically from public technical signals. It is not legal or financial advice.

Vet your next domain in under 10 seconds.

No signup. No credit card. No hidden quotas.

Start a free check →