Skip to content
Simoneiasimoneia.it
Guide · ART-001

7 signs your website is more exposed than you think

Seven problems anyone can see from the outside on a website or online shop: certificates, headers, forgotten files, open admin panels, public storage and spoofable email.

11/17/2026 · 6 min read

When people talk about website security, they often picture hackers breaking into complex systems. In practice, a large share of the problems we find at SMBs is visible from the outside, without forcing anything: you only need to look at what the site shows to everyone. Here are seven signs to check.

1. The HTTPS certificate is expired or about to expire

An expired certificate triggers a full-screen browser warning: visitors leave and customers wonder whether the site is safe. It often happens because renewal was "automatic" and at some point silently stopped working.

What to do: check the expiry date and make sure someone gets an alert at least two weeks ahead.

2. Security headers are missing

Security headers are instructions the site gives the browser: always use HTTPS (HSTS), don't run scripts from unknown sources (CSP), don't allow embedding in other people's pages. Without them the site still works, but it is easier to attack. They are among the best cost-to-benefit improvements available.

What to do: adding them is usually a configuration change of a few lines.

3. The site reveals which software it runs, and which version

Headers like Server: Apache/2.4.29, or a WordPress theme with a visible version, tell an attacker exactly which known flaws to look for. It is not serious on its own, but it speeds up anyone trying to get in.

What to do: hide version numbers and, above all, keep the CMS, plugins and server up to date.

4. Files that should not be public

Backup copies (backup.zip, site.sql), configuration files, development folders forgotten on the production server. These are common after a migration or a quick fix, and they sometimes contain passwords or customer data.

What to do: review what is reachable from the outside and remove anything that does not need to be online.

5. Admin panels open to everyone

Pages like /wp-admin, a database panel or a members area with no extra protection are constantly probed by automated bots using passwords stolen elsewhere. If access is only "username and password", sooner or later someone gets in.

What to do: two-factor authentication, limits on login attempts and, where possible, access only from authorized addresses.

6. User files reachable by anyone with the link

Documents, images or attachments uploaded by users and kept in public storage: anyone who knows (or guesses) the address opens them without logging in. It is one of the most underestimated problems in products with a customer area, and one of the ones that show up most often in our tests.

What to do: make storage private and serve files only through temporary links and authorization checks.

7. Anyone can send email in your domain's name

Without properly configured SPF, DKIM and DMARC, forging an email that appears to come from info@yourcompany.com is easy. It is the starting point of many scams against customers and suppliers ("the invoice changed, the new IBAN is…").

What to do: configure the three records and move DMARC from "monitoring only" to a policy that blocks fake emails.

How to tell where you stand

You can check several of these yourself, or use our free check: in seconds it verifies the certificate, headers, HTTPS redirect and email protection, looking only at public information.

For the points that require going deeper (exposed files, panels, storage) you need a real test, and a real test requires a written mandate: we never test other people's systems without authorization. If you want to understand what to do, book a call: we tell you honestly whether there is something to fix, and what.

For a concrete example of how these problems come to light, see the Get4oBack case.

→ Related case: Security test on Get4oBack marketing and app