What is this website?
Rogier Lankhorst originally launched Really Simple SSL in 2015 as a simple and performant solution to migrate WordPress sites to HTTPS/SSL. Back in 2015, getting WordPress sites up and running over HTTPS/SSL was often a cause for headaches. Website owners had to configure various aspects such as enabling a (performant) redirect from http to https, getting rid of mixed content and account for server-specific variables; to adjust their WordPress configuration accordingly for their websites to work
No listed local patterns observedHomepage-only analysis is not a malware clearance. Read the scope and findings below.
How to read this report
Safety Score evaluates observed signals. Evidence Confidence measures how complete, direct, fresh, and consistent those signals are.
No automated scan can guarantee that a website is safe.
Current report context
What changed since the last scan
- No earlier report to compare
What this scan could verify · 6 observed, 0 unavailable
Unavailable and unperformed checks are not clean results. The detailed evidence below remains the source for each conclusion.
Independent evidence brief
What we observed about really-simple-ssl.com
The latest scan examined 7 public pages on really-simple-ssl.com. Website descriptions below come from the site itself. Registration, connection and threat findings were checked separately.
Purpose and visible content
On its About page, the site says: Rogier Lankhorst originally launched Really Simple SSL in 2015 as a simple and performant solution to migrate WordPress sites to HTTPS/SSL. Back in 2015,…
Observed page title: Really Simple Security: Simple and Performant WordPress Security.
Registrar and domain history
Registered on Jun 26, 2015. Registrar: Combell NV.
Recorded expiry date: Jun 26, 2027. Registry data can change.
Connection and hosting evidence
The checked homepage returned HTTP 200.
A valid TLS certificate was observed, expiring Dec 29, 2026.
Threat checks and score context
External malware-provider coverage was unavailable. The report does not treat this missing check as a clean result.
Safety Score: 79/100. Evidence Confidence: 75%. These measure different things.
Community reviews of really-simple-ssl.com
No approved reviews yet
Visitor experiences are separate from the independent technical Safety Score.
Visitor opinions remain separate from the technical Safety Score.
Public content profile
Pages reviewed on really-simple-ssl.com
We sampled public pages from this website to understand its subject and contact paths. The titles and short descriptions below come from the website itself. They are not endorsements or independent safety findings.
Public page evidence
Topics and keywords observed on really-simple-ssl.com
These phrases were extracted locally from sampled public page metadata. They are observations, not search-volume or ranking estimates.
At a glance
Key findings
Report is current
The displayed evidence comes from the published immutable scan.
Confidence is separate
Unavailable evidence is shown as missing and never counted as clean.
Verify before sensitive actions
Check the exact URL and context before payments, credentials, or downloads.
Fully explainable
Why this score?
Threat providers were unavailable. The neutral uncertainty baseline is not a clean verdict.
Domain registration age and expiry were checked.
Observed DNS records and network address were checked.
Observed certificate validity and TLS protocol were checked.
Observed security header values were checked for basic protective settings. Empty values, disabled HSTS and unrecognized values receive no credit. This is not a complete browser-policy validation.
Observed site metadata and About page were checked. Publisher-supplied details are not independently verified.
Popularity is weak context, not proof of safety. Unranked sites use a neutral baseline.
Observed HTTP status and final connection scheme were checked.
Server-side analysis
Automated security checks
Local antivirus and phishing checks
Sampled scripts and pages
Resource analysis incomplete
6 resources checked · 25 script links observed on the homepage. Partial resource coverage.
ClamAV inspects the fetched homepage HTML on our server. New scans also sample up to four linked scripts and two collected internal pages, with size and time limits. Scripts are not executed. Other downloads, private server files and logged-in pages remain outside this check. A signature match needs investigation and can be a false positive. No match is not a whole-site safety guarantee.
Exact hostname lookup uses a downloaded Phishing.Database snapshot. It does not send this domain to an external lookup API or mark sibling subdomains as harmful. Not listed does not mean safe. Snapshot age is download age, not proof that every entry was recently revalidated.
Homepage HTML only · Eight local rule families · local-security-v2
Checks use the fetched page and redirect chain. Scripts are not executed, forms are not submitted, and linked files are not downloaded. This is not a malware clearance.
Page resource inventory
Counts describe the sampled HTML, not every resource loaded by the browser. External resources are common and are not automatically harmful.
No listed local patterns observed. The limited rule set cannot detect every threat or behavior.
External threat intelligence
Local checks do not query external reputation databases. An unavailable check is never a clean result.
Registration
Domain information
Infrastructure
Network & hosting
At a glance
Infrastructure summary
A compact view of the connection, DNS and security surface. These observations describe what the scanner could verify at scan time and do not prove ownership or ongoing availability.
Page telemetry
Observed page statistics
These counters describe the fetched response and sampled HTML. Script counts describe references in the markup, not a complete browser network log. Cookie counts cover observed response headers.
Encrypted transport
TLS certificate
Resolution
DNS footprint
DNSKEY presence does not verify the DNSSEC signature chain. Missing records can mean no record was returned or the lookup was unavailable.
104.26.12.183TTL —104.26.13.183TTL —172.67.73.16TTL —2606:4700:20::681a:cb7TTL —2606:4700:20::681a:db7TTL —2606:4700:20::ac43:4910TTL —bob.ns.cloudflare.comTTL —kayleigh.ns.cloudflare.comTTL —10 mx.spamfilter.ioTTL —0 issue "comodoca.com"TTL —0 issue "digicert.com; cansignhttpexchanges=yes"TTL —0 issue "letsencrypt.org"TTL —0 issue "pki.goog; cansignhttpexchanges=yes"TTL —0 issue "sectigo.com"TTL —0 issue "ssl.com"TTL —0 issuewild "comodoca.com"TTL —0 issuewild "digicert.com; cansignhttpexchanges=yes"TTL —0 issuewild "letsencrypt.org"TTL —0 issuewild "pki.goog; cansignhttpexchanges=yes"TTL —0 issuewild "ssl.com"TTL —google-site-verification=QekS_uBxPJCKmPwNCyizmsKQpJ4FT4LOAF6JeZaPt0YTTL —Sendinblue-code:7b4a9f57c1188a8d75e6753670a5d2c1TTL —v=spf1 include:spf.protection.outlook.com include:spf.sendinblue.com include:mailgun.org include:spf.spamfilter.io include:mail.zendesk.com -allTTL —DNS observations · no external lookup API
Domain email protection
Exact-host SPF and DMARC observations help the owner investigate email impersonation risks. They are separate from website malware checks and do not change the Safety Score.
What to do next
Review the records with your mail administrator. Inventory legitimate senders and test SPF and DKIM alignment before enforcing a stricter DMARC policy. Fix duplicate records and investigate overly permissive SPF rules.
This bounded check does not send email, probe SMTP, evaluate recursive SPF includes, verify DKIM signatures or apply organizational-domain DMARC inheritance. A missing subdomain record does not prove that no inherited protection exists. A DNS timeout is unknown, not an absent record. A policy record is not proof that messages authenticate successfully.
Responsible disclosure
security.txt
This is a public vulnerability-reporting contact file. Its presence does not prove that the website is safe and does not change the independent Safety Score.
Browser protections
Security headers
Response headers
Cookie protections
No Set-Cookie header was observed on the sampled homepage response. Other pages may set cookies separately.
Detected stack
Technologies
Versions are shown only when publicly exposed by the page or response headers. An observed version is not, by itself, proof of a vulnerability.
JavaScript library advisories
4 sampled JavaScript files checked locally with Retire.js. Database snapshot: 2026-10-12T02:40:13.167Z.
A version match is not proof that the website is infected or that an issue is exploitable here. Owners should review the advisory, check whether their code is affected and test an update. Up to four external script files are sampled, not every dependency, inline script or dynamically loaded resource.
Recommended maintenance checks
About this website
What the site says about itself
Rogier Lankhorst originally launched Really Simple SSL in 2015 as a simple and performant solution to migrate WordPress sites to HTTPS/SSL. Back in 2015, getting WordPress sites up and running over HTTPS/SSL was often a cause for headaches. Website owners had to configure various aspects such as enabling a (performant) redirect from http to https, getting rid of mixed content and account for server-specific variables; to adjust their WordPress configuration accordingly for their websites to work correctly over HTTPS/SSL.
This is publisher supplied information. The independent safety findings are shown separately.
Publisher supplied
Social profiles observed on this website
These links appeared on the website. We have not independently verified ownership of the linked accounts.
LinkedIn
GitHub
Structured facts
Website identity & response
Connection path
Redirect chain
No redirect hop was recorded for the sampled homepage.
Compared with the previous scan
What changed
A comparison will appear after the next completed scan.
Explainable matching
Digital fingerprint
Comparable components help find technically related websites. A match does not prove common ownership.
Material changes only
Change history
Show change history
No meaningful changes recorded yet.
Visual evidence
Website screenshot
For site owners
Show your verified trust report
Place this lightweight badge in your footer to show visitors an independent, dated WebsiteVirusScanner report. It can increase visitor confidence, but it never changes or guarantees the score.
Use the current report link so visitors can verify the evidence. A badge is a transparency signal, not a paid ranking boost.
Questions about really-simple-ssl.com
FAQ
Is really-simple-ssl.com safe to visit?
The latest Safety Score is 79/100 with 75% Evidence Confidence. This is a point-in-time assessment of observed technical signals, not a guarantee. Check the exact address and avoid entering payment details if anything looks unusual.
Did the scan detect malware on really-simple-ssl.com?
ClamAV found no signature match in the sampled homepage HTML. External scripts, downloads and private server files were not checked. This is not a whole-site malware clearance.
When was really-simple-ssl.com registered?
The public registry record shows Jun 26, 2015. Registration details may be privacy-protected or updated later.
Did really-simple-ssl.com have a valid TLS certificate?
The scanner observed a valid TLS certificate using TLSv1.3. A valid certificate alone does not establish that the site is safe.
How does really-simple-ssl.com describe itself?
The website's About page describes its purpose in the report above. This is publisher-supplied information and is separate from independent security findings.
Can a paid listing change this website's score?
No. Premium placement and owner-supplied pages are labelled separately. Technical evidence, the Safety Score and moderation decisions remain independent.
Share your experience with really-simple-ssl.com
Community reviews are moderated and remain separate from the technical Safety Score.
Write review →