Blog
Contact
Sign in
Scan complete
C
77/100
niezapominajka.pl
12 high-risk issues to fix.
16/16
checks
46
passed
finished
Scan timestamps
Created
Jul 17, 2026, 10:50 AM
Started
Jul 17, 2026, 10:50 AM
Finished
Jul 17, 2026, 10:50 AM
Updated
Jul 17, 2026, 10:50 AM
Export PDF
Re-scan
Findings by severity
67 results
0
Critical
12
High
6
Medium
3
Low
46
Pass
Report coverage
87.66%
28 skipped - these limit completeness.
28 skipped
All
95
High
12
Medium
6
Low
3
Pass
46
Skipped
28
Email
69%
Domain Alignment (DMARC)
Learn how it works
Info
6/7 pass
Domain Alignment (DMARC)
DMARC aggregate reporting is not configured
The DMARC record does not request aggregate reports, which reduces visibility into authentication failures.
Medium
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
3/4 pass
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 Integrity (DNSSEC)
Learn how it works
Info
5/7 pass
DNS Integrity (DNSSEC)
DNSSEC uses a discouraged algorithm
DNSSEC validation can succeed, but one or more algorithms or digest types are not recommended for new deployments.
Medium
DNS Integrity (DNSSEC)
NSEC3 iterations exceed the recommended value
The zone uses NSEC3 with a non-zero iterations count, which RFC 9276 recommends against due to unnecessary CPU cost for validating resolvers.
Low
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 Configuration
Learn how it works
Info
4/6 pass
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
TLS Configuration
Weak elliptic curve accepted for key exchange
The server negotiates an elliptic curve below 256 bits for at least one ECDHE cipher suite. Weak curves reduce the effective security margin of the key exchange well below modern standards.
High
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
1/7 pass
HTTP Security Headers
HSTS is not enforced
The site does not send a usable Strict-Transport-Security header, so browsers do not automatically upgrade future requests to HTTPS.
High
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
Clickjacking protection is missing
The site does not restrict framing through CSP frame-ancestors or a usable X-Frame-Options value, so it can be embedded in a frame on any origin.
High
HTTP Security Headers
MIME sniffing is not disabled
The site does not send X-Content-Type-Options: nosniff, so browsers may MIME-sniff a response and interpret it as a different, potentially executable content type.
High
HTTP Security Headers
Referrer-Policy is not declared
The site does not send a Referrer-Policy header. Modern browsers default to a reasonably safe behavior, but the site does not explicitly guarantee it.
Medium
HTTP Security Headers
Permissions-Policy is missing or ineffective
The site either does not send a Permissions-Policy header, or the header only lists directives with a wildcard allowlist that does not restrict anything.
Medium
Feedback
