Try Dynamic Growth free for 7 days. 1 free credit. Cancel any time. Start free trial

SSL Checker and Website Security Check

SSL checker and website security checker: certificate dates, HTTPS redirect, HSTS and security headers with copy-paste fixes. 1 credit per run.

Many website security problems are plain configuration gaps that anyone can see from the outside. A certificate that is about to expire turns your site into a full-page browser warning. A missing redirect leaves an insecure version of your pages open. Missing security headers leave it to each visitor's browser to guess how strict to be. These are small settings, and they are easy to miss because the site still looks fine.

The Security and SSL Check from Dynamic Growth is an automated service. It costs 1 credit and needs only your website URL. Our software looks at your site the way an outside visitor does. It checks your SSL certificate and its expiry date, whether HTTP redirects to HTTPS, HSTS, the main security headers, cookie flags, version details that your server gives away, and mixed content. For the headers that are missing, the report includes copy-paste fixes. You can start with the free 7-day trial, which comes with 1 credit and costs nothing for 7 days.

What you get

Certificate and expiry, HTTPS redirect, security headers and mixed content, with fixes.

SSL certificate and expiry

Whether your certificate is valid, who issued it, which names it covers and the date it expires. An approaching expiry date is listed clearly so you can renew before visitors see a warning.

HTTP to HTTPS redirect check

Whether the plain HTTP version of your site sends visitors to the secure version, and whether it does so in a single step. A missing or broken redirect leaves a second, unprotected copy of your pages reachable.

HSTS check

Whether your site sends the Strict-Transport-Security header, which tells browsers to use HTTPS only. The report shows the setting it found and whether it is present at all.

Security header review

Whether Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy are set. Each one is marked present or missing, with a short note on what it does.

Cookie flag check

The cookies your site sets and whether they carry the Secure, HttpOnly and SameSite flags. Cookies without these flags are easier to misuse, particularly any that hold a login session.

Version leaks and mixed content

Server and software names or version numbers that your responses reveal, and any images, scripts or stylesheets loaded over plain HTTP on a secure page. Both are visible to outsiders and both have simple fixes.

Copy-paste fixes

For each missing header, a ready-to-use line you can add to your server or hosting configuration. Where the right setting depends on your site, the report says so, so you can test before you apply it.

What we need from you

Your website URL.

  • SSL certificate and expiry date
  • HTTP to HTTPS redirect and HSTS
  • Security headers and cookie flags
  • Version leaks and mixed content, with header fixes

Why check your site's security setup

Visitors judge security by what their browser shows them. An expired certificate or a page that loads some files over plain HTTP brings up a warning or removes the padlock. Most people leave when they see one. If your ads send traffic to such a page, you pay for clicks that end at a warning screen. Checking the certificate and the redirect is the fastest way to avoid that.

Headers add protection and cost nothing to turn on. They tell the browser what your pages may load, whether they may be placed inside another site's frame, and how much information to share when a visitor clicks a link. Most sites run without them simply because nobody set them up. Adding them takes a few lines in your server or hosting settings.

This check has a clear limit, and you should know it before you buy. It reads what your site shows publicly. It is not a penetration test and cannot see inside your server, your code or your database. A clean report means the visible setup is in order, which says nothing about resistance to every attack. For deeper assurance you would need a security professional to test the system directly.

How it works

  1. Enter your website URL

    Type your site address and confirm the run. It costs 1 credit, and the URL is the only input: no uploads, no passwords and no server access.

  2. Automatic outside check

    Our software connects to your site as a visitor would. It reads the certificate, follows the redirect, collects the response headers and cookies, and scans the page for files loaded over HTTP.

  3. Read the report

    The report appears in your dashboard. Each check is marked as passed, needing attention or missing. Start with the certificate and redirect, then read through the headers.

  4. Apply the fixes yourself

    Add the suggested headers in your server or hosting panel, or send the copy-paste lines to your developer. Test your site after each change, particularly a Content-Security-Policy, which can block things your pages depend on.

Common problems the check finds

A certificate close to expiry

Certificates expire, and auto-renewal can stop working after a hosting change without any notice. When one lapses, browsers show a warning page in place of your site. The report shows the expiry date so you can renew in good time.

No redirect from HTTP to HTTPS

If someone types your address without https, they may land on the insecure version. A single redirect to the secure address fixes this and keeps search engines from seeing two copies of the site.

Missing security headers

Without X-Frame-Options or a frame rule in a Content-Security-Policy, another site can load your page inside a frame. Without X-Content-Type-Options, browsers may guess file types. The report lists which are missing and gives you the line to add.

Mixed content

A secure page that loads an image or script over HTTP loses its full padlock, and some browsers block the file. The report lists the files so you can change their addresses to HTTPS.

Cookies without protective flags

Session cookies sent without Secure or HttpOnly are easier to intercept or read. Your platform usually has a setting to add them. The report names the cookies it found without the flags.

What the check looks at

  • Certificate validity and days remaining. Whether the certificate is currently valid and how many days are left before it expires. This is the item that causes the most visible damage when it is missed.
  • Redirect behavior. Where the HTTP address of your site ends up and how many steps it takes. One direct step to HTTPS is the aim.
  • HSTS setting. Whether the header is present and how long browsers are told to remember it. A longer period gives stronger protection.
  • Header presence. A present or missing result for each of the five main security headers. The report does not grade how strong your policy values are beyond noting what it found.
  • Cookie flags. Which of Secure, HttpOnly and SameSite each cookie carries.
  • Information leaks and insecure files. Server or software version text in your responses, and the count of files on the page loaded over plain HTTP.

Do it yourself or run the check?

You can check most of this yourself. Your browser's padlock shows the certificate details, the developer tools show response headers and cookies, and free online header checkers exist. If you are comfortable reading raw headers, that approach works well, and you will learn what each line means.

The automated check suits owners who want one readable result. It covers the certificate, redirect, headers, cookies and mixed content in one run, and writes the fixes out in a form you can paste. It looks at one URL, which is usually your homepage, and it only sees what the server sends to an outside visitor. It cannot test your login, your forms, your plugins or your hosting account, and it does not test for vulnerabilities. If your site handles payments or personal data, treat this as a first look and arrange a proper security review as well.

Who it's for

Best for

  • Owners who want to confirm the certificate and HTTPS setup are in order
  • Advertisers who send paid traffic to a site and cannot risk a browser warning
  • Businesses that recently changed hosting, moved domains or installed a new certificate
  • Developers who want a quick header checklist with ready-made lines to add

Not the right fit if

  • Anyone who needs a penetration test or a check for hacked files and malware
  • Teams that want to examine their server, code or database, since the check sees only the public surface
  • Sites that need ongoing certificate monitoring, since this is a one-off report

An SSL certificate checker and website security checker

The Security and SSL Check works as an SSL certificate checker and a website security checker for the parts visible from outside. It reads the certificate and its expiry date, the HTTP to HTTPS redirect, HSTS, the main security headers, cookie flags and mixed content, then gives copy-paste fixes for what is missing.

It is not a website security scanner in the sense of a penetration test or a vulnerability scan, and it says what it did not test. Site owners in the USA, the UK, Europe, the Middle East and Latin America use it before launches and after certificate renewals.

Frequently asked questions

Is this a penetration test?

No. Nothing is attempted against your site. The software requests your pages like an ordinary visitor and reports what comes back: the certificate, headers and cookies.

What does it cost?

1 credit per check. The free 7-day trial includes 1 credit and costs nothing for 7 days, which covers one run.

Which headers does it check?

Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy, each marked present or missing. HSTS (Strict-Transport-Security) has its own separate check.

Is it safe to paste the suggested header fixes?

Most are low risk, but a Content-Security-Policy can block scripts, fonts or images your pages use. Add it carefully, test your site afterward, and be ready to adjust. The report notes where a setting depends on your site.

Will it find malware or a hacked site?

No. It does not scan your files or your server, only the public setup. If you think your site has been compromised, speak to your host or a security professional.

Does it fix anything for me?

No. The report lists what is missing and gives you lines to add. You or your developer apply them, and nothing on your site changes until then.

How much does security and ssl check cost?

Security and SSL Check costs 1 credits. On the Starter plan ($29 for 10 credits) that is about $2.90, on Growth ($59 for 25 credits) about $2.36, and on Scale ($129 for 60 credits) about $2.15. Ad spend is always paid separately to the ad platforms.

What do you need from me?

Your website URL.

Glossary

SSL certificate
A file that lets a site use HTTPS and proves the site is who it claims to be. It has an expiry date and must be renewed.
HSTS
A header that tells browsers to load your site only over HTTPS, even if someone types the plain HTTP address.
Content-Security-Policy
A header that lists where a page may load scripts, images and other files from. It limits what an injected script could do.
Mixed content
Files loaded over plain HTTP on a page that is otherwise secure. Browsers may block them or remove the padlock.

Run the Security and SSL Check on your site

Security and SSL Check: 1 credit per run, from $2.15 on the Scale plan. The free trial credit covers it.

7 days free · 1 free credit · cancel any time