movecommons.org

#FFB3BF96 · Very Safe
95 / 100
AnalyzeDigest · movecommons.org — Report card
104.21.6.106 Valid HTTPS 16.2 years OVH sas Updated

movecommons.org — independent inspection

Below: every public infrastructure fact our scanner could find on movecommons.org, mapped onto an objective 0-100 score.

Technical Information

IP Address104.21.6.106
Server LocationUnknown
ISP / ProviderUnknown
SSL Certificate Valid HTTPS
SSL IssuerWE1
Valid Until2026-08-19
RegistrarOVH sas
Registered On2010-04-05
Expires On2027-04-05
Domain Age16.2 years

What we observed

Looking at movecommons.org from the outside, the most important data points are its hosting country (Unknown), the SSL state (OK) and the registration footprint (OVH sas).

Time on the open web

movecommons.org has been visible to public DNS for roughly 16.2 years. That is enough history to leave a reputation footprint, which we factor into the score.

Encryption (HTTPS)

HTTPS check returned OK. A valid TLS certificate is the bare minimum any modern site should ship — its absence is a serious red flag.

Hosting & infrastructure

The domain currently resolves to a server in Unknown, served by Unknown. Hosting location does not equal trust, but it tells you which jurisdiction handles the data.

Comparable domains

Sites with similar metadata to movecommons.org — 16.2 yrs, Unknown hosting, valid SSL — typically include both legitimate businesses and rebranded shells. Treat the score as one signal among several.

Conclusion

After fusing DNS, TLS, RDAP and GeoIP signals, our automated score for movecommons.org sits at 95/100 (very_safe). Use it as a guideline, not a guarantee.

Frequently Asked Questions

How often is movecommons.org 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 movecommons.org?
The current network announcement comes from Unknown, with the IP geo-located in Unknown.
Where do I file a complaint about movecommons.org?
You can file a takedown notice with the registrar (OVH sas) or the hosting ISP (Unknown). Each maintains a public abuse channel.
Does movecommons.org have IPv6?
Our DNS lookup returns AAAA-record presence as part of the report. If absent, movecommons.org is currently IPv4-only.

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