Analysis modules

What does each module check?

Every scan runs all seven modules simultaneously. Here's what each one checks and what risks it covers.

DomainScored performs a complete web security audit by analyzing the seven most common risk vectors of any domain. The analysis is remote — you don't need to install anything or modify the site being analyzed — and completes in under 60 seconds.

If the analysis detects a problem, each module includes specific fix instructions tailored to your server. For each vulnerability you can also consult the corresponding security guide.

01
SSL / TLS
Certificates & encryption

Analyzes the SSL/TLS certificate: expiry date, certificate authority, protocol versions (TLS 1.0–1.3) and cipher suites. Detects expired, self-signed or broken trust chain certificates.

Certificate validityObsolete TLS 1.0/1.1Trust chainOCSP / CRL
Consequences of non-compliance

An expired certificate or outdated TLS version triggers security warnings in all browsers, destroying user trust. Without modern encryption, any attacker on the same network can intercept credentials, payment data and private communications (man-in-the-middle attack).

02
HTTP Headers
Security headers

Examines HTTP response headers for missing or misconfigured settings that expose the site to XSS, clickjacking or server information leaks.

Content-Security-PolicyStrict-Transport-SecurityX-Frame-OptionsReferrer-Policy
Consequences of non-compliance

Without CSP, an attacker can inject malicious scripts to steal user sessions (XSS). Without HSTS, connections can silently downgrade from HTTPS to HTTP. Without X-Frame-Options, the site is vulnerable to clickjacking where users unknowingly execute unauthorized actions.

03
DNS & Email
Infrastructure & authentication

Reviews DNS configuration and email authentication mechanisms (SPF, DKIM, DMARC) to prevent domain impersonation and phishing.

SPF recordDKIM signatureDMARC policyReverse PTR lookup
Consequences of non-compliance

Without SPF and DMARC, anyone can send emails appearing to come from your domain to deceive customers or employees. This enables highly effective spear-phishing attacks, severely damaging domain reputation and potentially resulting in legal liability for impersonation.

04
Blacklists
IP & domain reputation

Checks whether the server IP or domain appears in international spam, malware or phishing blacklists. Queries 11 DNSBL/SURBL reputation sources in real time.

Spamhaus ZENSpamhaus DBLSURBL multiBarracuda BRBLAbuseat CBL
Consequences of non-compliance

If your IP or domain is blacklisted, all your emails go straight to spam, blocking customer communications. Browsers may show dangerous site warnings, driving traffic to zero. Restoring reputation requires a manual process that can take weeks and directly impacts revenue.

05
Technologies
Stack exposed to attackers

Detects what technologies the site reveals through HTTP headers, cookies and HTML. Identifies exact versions of CMS, web servers and JavaScript frameworks visible from the outside.

Server / X-Powered-ByCMS (WordPress, Drupal…)JS FrameworksMeta generator tag
Consequences of non-compliance

Exposing exact stack versions enables attackers to find known CVEs and launch automated exploits within minutes. Most mass attacks are not targeted: bots scan the internet looking for specific vulnerable versions. Hiding this information is the first line of defence.

06
Cookies & GDPR
Cookie legal compliance

Analyzes the cookies set by the site, classifies them (technical, analytics, advertising, third-party) and checks whether a consent banner is present when legally required, under GDPR and Spain's LSSI-CE.

Consent bannerThird-party cookiesSecure / HttpOnly / SameSite flagsLegal classification
Consequences of non-compliance

Setting analytics or advertising cookies without prior consent breaches the LSSI-CE (art. 22.2) and the GDPR, with fines of up to €30,000 from the Spanish data protection authority. Cookies missing the Secure or HttpOnly flags also make session theft easier.

07
Exposed Paths
Sensitive files & paths

Checks whether files or paths that should never be public (.git repositories, database backups, .env files, server information panels) are accessible from the outside.

.git / .svn exposedBackups (.sql, .zip, .bak).env filesphpinfo / server-status
Consequences of non-compliance

An exposed Git repository or .env file can reveal the entire source code, API keys and database passwords. It's one of the most common paths to a full website compromise.

How to fix the detected issues?

DomainScored's security guides explain step by step how to correctly configure SSL/TLS, HSTS, SPF/DKIM/DMARC, Content-Security-Policy, blacklists and GDPR cookie compliance.

View security guides →
We use necessary cookies to keep you signed in and protect you against CSRF attacks. If you accept, we will also load Google advertising, which sets its own cookies. If you decline, the site works exactly the same.