Security basics
What does the Security basics cluster cover?
AdminKit groups this topic into the Security basics cluster: TLS certificates, HTTP security headers and open ports are the fundamentals every internet-facing service should get right, independent of which protocol, operating system or cloud provider it runs on — most breaches start with one of these basics left unchecked.
Guides (8)
All guides →- Checking TLS Certificate Chain Completeness | AdminKit Guide
- How to Avoid an Expired TLS Certificate Outage
- How to Read an HTTP Security Headers Result | AdminKit Guide
- Evaluating HTTP Security Header Strength | AdminKit Guide
- How to Read a TLS/SSL Certificate Result | AdminKit
- How to Read an Open Ports Scan Result | AdminKit Guide
- HSTS and HSTS Preload Explained | AdminKit Guide
- Wildcard vs SAN Certificates Explained | AdminKit
Glossary (0)
Full glossary →No glossary terms in this cluster yet — see the full glossary.
Comparisons (6)
All comparisons →- Best Free HTTP Security Header Analyzers (2026) | AdminKit
- AdminKit vs Qualys SSL Labs: a sourced comparison | AdminKit
- AdminKit vs SecurityHeaders.com, compared | AdminKit
- AdminKit vs Shodan and Censys: Sourced Comparison
- Best free open port check tools (2026) | AdminKit
- Best free SSL/TLS certificate checkers (2026) | AdminKit
Solutions (2)
All solutions →- AdminKit for Developers: Check TLS & Headers Free Developers can check TLS certificate expiry, security headers, and MCP endpoint exposure for free. Script the same checks in CI/CD with the AdminKit Check API.
- AdminKit for Shops & Cafés: Free Network Checks Shops and cafés can check their network exposure for free with AdminKit. Netbase can also review and protect your shop network for you.
Related clusters
IP & network
Your public IP, subnet and routing determine who can reach your connection and how it is addressed on the internet — the starting point for almost every other check on this site.
Machine protocols
MQTT, Modbus, RDP, VNC and the other protocols your devices and legacy systems speak were mostly designed for trusted local networks, not the open internet — exposing one is a common way in for an attacker.
Frequently asked questions
What's the difference between an expired TLS certificate and a misconfigured one?
An expired certificate has a valid chain and hostname but its notAfter date has passed, which browsers treat as a hard failure; a misconfigured certificate might still be within its validity window but have an incomplete chain, the wrong hostname in its SAN list, or a weak signature algorithm (TLS 1.3 itself is specified in RFC 8446) — each produces a different browser warning, not just a generic 'not secure' message.
Which HTTP security headers actually matter?
The headers with the most practical impact are a Content-Security-Policy to limit what scripts can run, Strict-Transport-Security to force HTTPS on every future visit, and X-Content-Type-Options: nosniff to stop the browser from guessing a file type — the OWASP Secure Headers Project documents the full set and what each one defends against.
Is an open port always a security risk?
No — a port is only a risk if the service listening on it is unauthenticated, unpatched or wasn't meant to be reachable from where the scan found it; a web server correctly listening on 443 is an intentionally open port. What matters is whether the service behind the port should be reachable from that network and whether it's running securely, which is what AdminKit's open ports and HTTP headers checks are built to surface.