reopensafely.org is registered with whois.publicinterestregistry.org. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
0 of 5 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed reopensafely.org. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
No similar domains registered in the last 90 days.
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is reopensafely.org’s name taken on other extensions?
No reviews yet. Used reopensafely.org? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
reopensafely.org has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
reopensafely.org is registered through whois.publicinterestregistry.org. See WHOIS →
Raw registry data for reopensafely.org. May be redacted by privacy services.
Domain not found. >>> Last update of WHOIS database: 2026-11-01T15:11:45Z <<< Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with reopensafely.org. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
We couldn't find an IP address for reopensafely.org's web or mail servers to check.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 1 Nov 2026.