Scoring methodology
Every Vernax check returns a score from 0–100. Here you'll learn which individual checks exist, how they're weighted and what the status values mean.
Which checks map to GDPR, ISO 27001, BSI and NIS2 is shown in the standard coverage.
Formula
Each check has a weight (in percent) and returns a status. The status determines the multiplier:
1.0
0.5
0.0
not weighted
Only the weights of checks that actually ran count — disabled checks or ones missing in context (e.g. CVE lookup for verified domains only) don't drag the score down. Info checks don't count at all – they only provide additional information.
Mail Check
Assesses whether emails from your domain are tamper-proof (SPF, DKIM, DMARC) and delivered encrypted (STARTTLS) — and whether your mail server IPs are on spam blocklists.
| Check | Description |
|---|---|
| MX record | Existence and reachability of the mail server |
| SPF | Sender Policy Framework – authorized sender IPs |
| DMARC | Policy for authentication failures (p=none/quarantine/reject) |
| DKIM | Domain Keys Identified Mail – cryptographic signature |
| STARTTLS | Encrypted transport to the mail server |
| TLS version | At least TLS 1.2, ideally TLS 1.3 |
| Certificate | Validity of the mail server's TLS certificate |
| DNSBL | Check against IP blocklists (spam blacklists) |
| DBL | Check against domain blocklists |
| PTR record | Reverse DNS – IP points back to the hostname |
| DNSSEC | Cryptographic protection of the DNS zone |
| MTA-STS | Policy for enforced TLS connections |
| BIMI | Brand Indicators for Message Identification – logo in the inbox |
SSL Monitor
Checks your website's TLS certificate for validity, hostname and expiry, rates the protocol version and verifies enforced HTTPS redirection.
| Check | Description |
|---|---|
| Certificate valid | Certificate present, not expired, hostname matches |
| Expiry date | Days until expiry – warn < 30 days, fail if expired |
| TLS version | TLS 1.2 = warn, TLS 1.3 = OK, older versions = fail |
| HSTS | HTTP Strict Transport Security header present |
| HTTP redirect | HTTP requests are redirected to HTTPS |
DNS Monitor
Checks the basic configuration of your DNS zone: nameserver redundancy, SOA, CAA records, DNSSEC signing and protection against unauthorized zone transfer (AXFR).
The "All DNS records" check (A, AAAA, MX, TXT, …) is info-only and does not count toward the score.
| Check | Description |
|---|---|
| DNS snapshot | Comparison with the previous scan – unexpected changes are flagged |
| Nameservers | At least 2 NS records, all reachable and consistent |
| SOA record | Start of Authority present and correctly configured |
| CAA records | Certification Authority Authorization – which CAs may issue certificates |
| DNSSEC | Cryptographic protection of DNS responses |
| AXFR protection | Zone transfer from outside not possible (zone-walking protection) |
Domain Monitor
Monitors the lifecycle and registry protection of your domain – expiry date, EPP locks, nameserver match, registrar and WHOIS privacy.
| Check | Description |
|---|---|
| Expiry date | Days until domain expiry – warn < 30 days, fail if expired |
| EPP status | Registry status of the domain (clientDeleteProhibited, serverHold, …) |
| NS match | Nameservers in WHOIS and DNS match |
| Registrar | Registrar known and reachable |
| Domain age | Young domains (< 1 year) are considered riskier |
| Privacy protection | WHOIS privacy active – prevents exposure of personal data |
CT Monitor
Watches the Certificate Transparency logs for newly issued certificates for your domain – e.g. from unknown CAs or for unexpected subdomains (shadow IT).
| Check | Description |
|---|---|
| Certificate count | Unusually many certificates can indicate abuse |
| Unknown CA | Certificates from untrusted certificate authorities |
| Expiring certs | Certificates expiring in < 30 days |
| Subdomains | Unknown subdomains in CT logs – possible shadow IT |
| Reachability | Certified hosts are actually reachable |
Web Security
Examines your website's HTTP security configuration: HTTPS enforcement, security headers (HSTS, CSP …), exposed server information, open ports and known CVEs.
| Check | Description |
|---|---|
| HTTPS | Website reachable only via HTTPS |
| HSTS | Strict-Transport-Security header with sufficiently long max-age |
| Content Security Policy | CSP header present and not too permissive |
| Security headers | X-Frame-Options, X-Content-Type-Options, Referrer-Policy, … |
| Server info | No disclosure of server version/technology in headers |
| Open ports | No unexpected open ports (e.g. admin interfaces) |
| Server CVEs | NVD lookup of the exposed server version (verified domains only) |
Reputation Check
Checks the web and mail IPs as well as the domain itself against common spam, phishing and malware blocklists to catch reputation damage to deliverability early.
Blocklists that don't answer our queries (resolver blocking) are reported as info "not checkable" and don't count toward the score.
| Check | Description |
|---|---|
| Web-IP blacklists | Domain A/AAAA IPs against Spamhaus ZEN, Barracuda, SpamCop |
| MX-IP blacklists | Mail server (MX) IPs against the same blacklists |
| Domain blocklists | Domain against Spamhaus DBL and SURBL, with categorization (spam/phishing/malware) |
| Google Safe Browsing | Google's threat lists (malware, phishing) – omitted if no API key is configured |
Exposure Check
Actively probes for accidentally public, confidential paths – such as .git directories, .env files, database backups or open admin panels (verified domains only).
Only for domains verified in the workspace — the check deliberately requests potentially confidential paths. Unverified domains only get a notice.
| Check | Description |
|---|---|
| Version control (.git) | Publicly reachable .git/ directory (HEAD, config) — source code leak incl. history |
| Environment files (.env) | .env / .env.production reachable — almost always secrets in plaintext |
| Backups & databases | SQL dumps, .zip/.tar.gz archives, SQLite files in the web root |
| Config & meta files | .htpasswd, config.php.bak, .DS_Store and similar leaks |
| Admin panels & listings | phpMyAdmin, Traefik dashboard, directory listings (warning) |
Datenschutz-Check
Statically analyzes the homepage for GDPR-relevant third parties – remotely loaded Google Fonts, trackers, third-country transfers and cookies set before consent.
Static analysis (HTML + linked CSS). Resources loaded via JavaScript and cookies set only through interaction are not captured. Not legal advice.
| Check | Description |
|---|---|
| Google Fonts | Loaded remotely from fonts.googleapis.com/gstatic.com — IP transfer to the US (Munich court ruling) |
| Tracking services | Google Analytics, Meta Pixel, Hotjar & co. — only permitted after consent |
| Third-country transfer | Resources from typical third countries (US CDNs); requires a legal basis (warning) |
| Cookies before consent | Cookies set by the server on first visit — only strictly necessary ones allowed (warning) |
| Consent banner | Detected CMP (Cookiebot, Usercentrics, Borlabs …) — info, no score penalty |
Status values
OK
The check fully passed. Full contribution to the score.
Warn
The configuration is present but could be improved. 50% of the weight.
Fail
The check did not pass. No contribution to the score (multiplier 0).
Info
Purely informational, no scoring impact. Shows e.g. existing DNS records.