Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
trackyserver.com scored 88/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Security Headers, Cookie Security. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support 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 trackyserver.com compares
Grade distribution across 2445 companies we've scanned. trackyserver.com scores better than 81% 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
trackyserver.com — Grade B+ (88/100)
2445 companies scanned
Security checks
Each check inspects a different part of trackyserver.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
1/5 security headers present. Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Cookie Security
Strengths: 1 cookie(s) analyzed. Issues: 1/1 cookie(s) missing Secure flag (PHPSESSID); 1/1 cookie(s) missing HttpOnly flag (PHPSESSID); 1/1 cookie(s) missing SameSite attribute (PHPSESSID).
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
DNS Configuration
Strengths: 2 nameservers configured (nia.ns.cloudflare.com., dale.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
MX Records & Mail Provider
Strengths: Mail handled by mx00.1and1.fr; 2 MX record(s) configured; Multiple MX records provide redundancy; All MX records share the same priority (10) — round-robin load balancing (no primary/backup distinction).
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.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: mail).
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=15768000s (182 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
security.txt (RFC 9116)
Strengths: security.txt found with 4 field(s); Contact: ; Encryption key provided for secure reporting; Disclosure policy: ; Security hiring link included. Issues: Missing 'Expires' field (required by RFC 9116); Not PGP signed (recommended for authenticity).
CVE Exposure
Detected technologies: cloudflare, PHP/8.1.2-1ubuntu2.23. (cloudflare detected but excluded from CVE matching — upstream infrastructure). No high or critical CVEs found for detected versions.
Certificate Hygiene
Strengths: Certificate valid, 60 days remaining; Issued by Google Trust Services; 301 certificates logged in CT; Certificates from 8 CAs: "CloudFlare, "Cloudflare, COMODO CA Limited. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
2 items
Steps to improve trackyserver.com's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy)
4 of 5 recommended security headers are missing on trackyserver.com: CSP, 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-Frame-Options: SAMEORIGIN (use DENY only if you never embed your pages in iframes)
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://trackyserver.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for trackyserver.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec trackyserver.com
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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: mail).
SPF Record
Present
v=spf1 include:_spf.perfora.net include:_spf.kundenserver.de -all
Security Headers
1/5 present
Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=15768000s (182 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 60 days remaining; Issued by Google Trust Services; 301 certificates logged in CT; Certificates from 8 CAs: "CloudFlare, "Cloudflare, COMODO CA Limited. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (nia.ns.cloudflare.com., dale.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.