Report ID: #28DB9BB5

encrypt.me

Valid HTTPS Updated
65
Safe
AnchorValidate · encrypt.me — Report card
AnchorValidate · encrypt.me

encrypt.me — full safety report

Below you will find an independent technical breakdown of encrypt.me, gathered from public infrastructure data with no human bias.

At a glance

The fastest way to read encrypt.me: country Unknown, age ? yrs, SSL OK, registrar Unknown. Each of those points is expanded in the sections that follow.

Certificate health

The certificate currently presented by encrypt.me resolves as: OK. Valid certificates from a recognised CA are required for credit-card or login traffic.

Domain age

The domain has been registered for roughly ? years, which puts it in the "new" maturity bracket. Older domains are statistically less risky than freshly registered ones.

Server jurisdiction

The IP behind encrypt.me sits in Unknown, on infrastructure provided by Unknown. Disputes or DMCA notices typically follow that jurisdiction.

Should you trust encrypt.me?

Our score is purely technical. Sites with valid SSL, several years of history and a reputable registrar tend to score higher, but that does not exclude scams. Always combine this report with content judgement.

Where encrypt.me lands

On a 0-100 scale, our automated check places encrypt.me at 65 — that is the "safe" band. Combine with your own judgement for the final call.

Technical Information

IP Address
104.18.3.67
Server Location
Unknown
ISP / Provider
Unknown

SSL Certificate

SSL Certificate
Valid HTTPS
SSL Issuer
WE1
Valid Until
2026-08-28

Registrar

Registrar
Unknown

What looks good

  • No malware signature triggered our quick scan
  • Hosting country aligns with stated audience
  • Resolves over public recursive DNS (Google, Cloudflare, Quad9)
  • Uses modern HTTPS endpoints

What to watch

  • No structured Schema.org metadata published
  • Hosting on a residential/dynamic IP block
  • Technical signals alone cannot prove ownership

Vet your next domain in under 10 seconds.

No signup. No credit card. No hidden quotas.

Start a free check →

Frequently Asked Questions

What looks risky about encrypt.me?
For encrypt.me we look at: age ? yrs, SSL OK, registrar Unknown and hosting in Unknown. Any single weak point can drag the technical confidence down.
How often is encrypt.me 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 encrypt.me?
The current network announcement comes from Unknown, with the IP geo-located in Unknown.
Where do I file a complaint about encrypt.me?
You can file a takedown notice with the registrar (Unknown) or the hosting ISP (Unknown). Each maintains a public abuse channel.

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