Blog
Contact
Sign in
Scan complete
D
62/100
status.rknet.ovh
13 high-risk issues to fix.
16/16
checks
44
passed
finished
Scan timestamps
Created
Jul 17, 2026, 2:52 PM
Started
Jul 17, 2026, 2:53 PM
Finished
Jul 17, 2026, 2:53 PM
Updated
Jul 17, 2026, 2:53 PM
Export PDF
Re-scan
Findings by severity
64 results
0
Critical
13
High
2
Medium
5
Low
44
Pass
Report coverage
87.66%
31 skipped - these limit completeness.
31 skipped
All
95
High
13
Medium
2
Low
5
Pass
44
Skipped
31
Email
69%
Sender Authentication (SPF)
Learn how it works
Info
0/7 pass
Sender Authentication (SPF)
No SPF record found
The domain does not publish an SPF policy.
High
Domain Alignment (DMARC)
Learn how it works
Info
6/7 pass
Domain Alignment (DMARC)
DMARC reporting destination is not usable
The DMARC aggregate reporting destination is invalid, unsupported, or not authorized.
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
4/6 pass
CAA and Certificate Issuance Surface
Certificate issuance is not pinned
The CAA records authorize a CA but do not restrict issuance to a specific account or validation method.
Low
CAA and Certificate Issuance Surface
No S/MIME issuance policy is published
The domain does not publish an issuemail CAA property, so any CA may issue S/MIME certificates for its email addresses; note that issue and issuewild do not restrict S/MIME issuance.
Low
TLS
100%
TLS Configuration
Learn how it works
Info
4/6 pass
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
TLS Configuration
TLS 1.3 early data (0-RTT) enabled
The server accepts 0-RTT early data. Requests sent as early data can be replayed by an attacker without detection unless the application implements its own anti-replay protection. This is safe only for idempotent requests.
Low
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
3/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
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
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
