Blog
Contact
Sign in
Scan complete
D
60/100
gov.pl
Changed · score unchanged
Compare
11 high-risk issues to fix.
16/16
checks
41
passed
finished
Scan timestamps
Created
Jul 23, 2026, 11:38 AM
Started
Jul 23, 2026, 11:38 AM
Finished
Jul 23, 2026, 11:38 AM
Updated
Jul 23, 2026, 11:38 AM
Export PDF
Re-scan
Findings by severity
59 results
0
Critical
11
High
4
Medium
3
Low
41
Pass
Report coverage
87.73%
36 skipped - these limit completeness.
36 skipped
All
95
High
11
Medium
4
Low
3
Pass
41
Skipped
36
Email
69%
Domain Alignment (DMARC)
Learn how it works
Info
0/7 pass
Domain Alignment (DMARC)
No DMARC record found
The domain does not publish a DMARC policy.
High
Transport Encryption (SMTP TLS)
Learn how it works
Info
0/5 pass
Transport Encryption (SMTP TLS)
Mail servers are unreachable
No mail exchanger for the domain accepts SMTP connections on port 25, so inbound mail cannot be delivered.
High
Certificate Binding (DANE)
Learn how it works
Info
0/5 pass
Certificate Binding (DANE)
Mail servers are unreachable
No mail exchanger for the domain accepts SMTP connections on port 25, so inbound mail cannot be delivered.
High
Mail Servers (MX)
Learn how it works
Info
0/4 pass
Mail Servers (MX)
No MX records found
The domain does not publish MX records. Sending MTAs fall back to the A record, which is not a substitute for a proper MX configuration.
High
Mail Servers (MX)
Mail servers are unreachable
No mail exchanger for the domain accepts SMTP connections on port 25, so inbound mail cannot be delivered.
High
Transport Policy (MTA-STS)
Learn how it works
Info
0/6 pass
Transport Policy (MTA-STS)
Mail servers are unreachable
No mail exchanger for the domain accepts SMTP connections on port 25, so inbound mail cannot be delivered.
High
Transport Policy (MTA-STS)
MTA-STS DNS record is missing
The domain does not publish an MTA-STS TXT record, so sending servers cannot discover or enforce an MTA-STS policy.
High
TLS Reporting (TLS-RPT)
Learn how it works
Info
0/4 pass
TLS Reporting (TLS-RPT)
Mail servers are unreachable
No mail exchanger for the domain accepts SMTP connections on port 25, so inbound mail cannot be delivered.
High
TLS Reporting (TLS-RPT)
No TLS-RPT record found
The domain does not publish a TLS-RPT record. Sending servers cannot report TLS errors to this domain.
High
DNS
100%
DNS Health (Delegation & Exposure)
Learn how it works
Info
7/8 pass
DNS Health (Delegation & Exposure)
SOA serial does not use the recommended format
The SOA record is otherwise valid, but the serial number does not follow the recommended YYYYMMDDnn date format.
Low
CAA and Certificate Issuance Surface
Learn how it works
Info
1/6 pass
CAA and Certificate Issuance Surface
No CAA record is published
The domain does not publish a CAA record, so any publicly trusted certificate authority may issue certificates for it after standard validation.
Low
TLS
100%
TLS Certificate
Learn how it works
Info
8/9 pass
TLS Certificate
Certificate chain is trusted by only some trust stores
The certificate chain validates successfully in some trust stores but fails in others. Some clients (e.g. specific browsers, operating systems, or Java versions) will show a trust warning while others accept the connection normally.
Medium
TLS Configuration
Learn how it works
Info
2/6 pass
TLS Configuration
Deprecated TLS version accepted (TLS 1.0 / TLS 1.1)
The server accepts TLS 1.0 and/or TLS 1.1, both formally deprecated by RFC 8996. These versions lack support for modern authenticated encryption and are the underlying cause of several named attacks (e.g. BEAST against TLS 1.0 CBC ciphers).
High
TLS Configuration
Legacy cipher suites accepted (3DES / CBC in TLS 1.0)
The server accepts cipher suites weakened by the 64-bit block size of 3DES (SWEET32, CVE-2016-2183) and/or CBC-mode ciphers in TLS 1.0 (contributing factor to BEAST). Exploitation requires specific conditions (e.g. very large data transfers for SWEET32).
Medium
TLS Configuration
Cipher suites without forward secrecy accepted
The server accepts one or more cipher suites using static RSA or static (EC)DH key exchange. If the server's private key is ever compromised, an attacker with recorded traffic can decrypt past sessions negotiated with these cipher suites.
Medium
Web
100%
Disclosure Policy (security.txt)
Learn how it works
Info
0/4 pass
Disclosure Policy (security.txt)
security.txt is not present or not usable
The domain does not publish a usable security.txt file. Either both /.well-known/security.txt and /security.txt returned no file (404/401/403/410), or the location responded with HTTP 200 but non-text/plain content (typically an application page) or a body that is not valid UTF-8.
Medium
HTTP Security Headers
Learn how it works
Info
5/7 pass
HTTP Security Headers
Content-Security-Policy is not enforced
The site does not send an enforced Content-Security-Policy header, leaving no restriction on script execution, framing, or resource loading beyond what other headers provide.
High
HTTP Security Headers
Deprecated security headers are present
The response sends one or more deprecated headers (X-XSS-Protection, Expect-CT, or Public-Key-Pins) that modern browsers ignore or that carry their own operational risk (HPKP).
Low
Feedback
