Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
lotro-wiki.com scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: HSTS Header, Security Headers. Positive signals: TLS Configuration, TLS Protocol Support, DNS Configuration all passed.
2 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How lotro-wiki.com compares
Grade distribution across 2445 companies we've scanned. lotro-wiki.com scores better than 64% of them.
75
A+
24
A
180
A-
187
B+
71
B
342
B-
118
C+
112
C
308
C-
114
D+
93
D
226
D-
595
F
lotro-wiki.com — Grade B- (80/100)
2445 companies scanned
Security checks
Each check inspects a different part of lotro-wiki.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
Security Headers
None of the 5 recommended security headers are present (missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy). This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
MX Records & Mail Provider
Strengths: Mail handled by dot.sverilog.com; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
DNS CAA Records
Strengths: CAA records configured (1 record(s)). Issues: No iodef record — CA violations won't be reported to the domain owner.
MTA-STS & TLS Reporting
Strengths: MTA-STS enabled with enforce mode (strongest); MX patterns specified: dot.sverilog.com; Policy max_age: 7 days. Issues: No TLSRPT record — TLS delivery failures won't be reported to domain owner.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
DNS Configuration
Strengths: 2 nameservers configured (ns1.dot.sverilog.com., ns2.dot.sverilog.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
Detected technologies: Server. No version information exposed — CVE matching not possible (this is good practice).
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: mail). Issues: DMARC has no aggregate report URI (rua).
Certificate Hygiene
Strengths: Certificate valid, 80 days remaining; Issued by Let's Encrypt.
Recommended actions
2 items
Steps to improve lotro-wiki.com's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on lotro-wiki.com. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://lotro-wiki.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on lotro-wiki.com: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add a Content-Security-Policy header. Safe starting value (works with Google Fonts and inline styles/scripts): default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests. Test your site after adding it, then tighten over time by removing 'unsafe-inline'.
2
Add: X-Content-Type-Options: nosniff
3
Add: X-Frame-Options: SAMEORIGIN (use DENY only if you never embed your pages in iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://lotro-wiki.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: mail). Issues: DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 mx -all
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Valid
Strengths: Certificate valid, 80 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 2 nameservers configured (ns1.dot.sverilog.com., ns2.dot.sverilog.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.