Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
orf.at scored 78/100, meeting baseline requirements but with 7 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: MX Records & Mail Provider, DMARC / Email Security, Known Breaches all passed.
4 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 orf.at compares
Grade distribution across 2379 companies we've scanned. orf.at scores better than 59% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
112
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
orf.at — Grade C+ (78/100)
2379 companies scanned
Security checks
Each check inspects a different part of orf.at's public security setup. Green means healthy, yellow needs attention, red is a problem.
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 (ns4.apa.net., ns3.apa.at.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
HSTS Header
HSTS configured with max-age=2592000s (30 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.
TLS Protocol Support
Strengths: TLS 1.2 supported; TLS 1.2 supported (consider enabling TLS 1.3). Protocol support: TLS 1.3: No, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Certificate Hygiene
Strengths: Certificate valid, 99 days remaining; Issued by Entrust Limited; 2096 certificates logged in CT. Issues: Certificates issued by 17 different CAs (threshold: 8 for 2096 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
MX Records & Mail Provider
Strengths: Mail handled by mx12.orf.at; 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).
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: mail).
Known Breaches
No known breaches found in public disclosure databases.
security.txt (RFC 9116)
Strengths: security.txt found with 7 field(s); Contact: mailto:[email protected]; Expires in 283 days (2026-12-31T23:00:00.000Z); Disclosure policy: https://der.orf.at/vdp100.html; Canonical URL specified; Preferred languages: en, de; Security hiring link included; Acknowledgments/hall-of-fame link included. Issues: Not PGP signed (recommended for authenticity).
Security Headers
4/5 security headers present. Missing: X-Frame-Options.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
CVE Exposure
Detected technologies: Apache. No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
4 items
Steps to improve orf.at's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for orf.at 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 .at TLD
4
Verify: dig +dnssec orf.at
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://orf.at | grep -i strict
3
Upgrade to TLS 1.3
orf.at negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect orf.at:443 -tls1_3
4
Review certificate configuration
Certificate issues found for orf.at: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: mail).
SPF Record
Present
v=spf1 a:orf.at a:ips.orf.at mx:orf.at include:spf.mailjet.com include:spf.eyepinnews.com include:sp
Security Headers
4/5 present
Missing: X-Frame-Options
HSTS
Not enabled
HSTS configured with max-age=2592000s (30 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.
SSL Certificate
Issues
Strengths: Certificate valid, 99 days remaining; Issued by Entrust Limited; 2096 certificates logged in CT. Issues: Certificates issued by 17 different CAs (threshold: 8 for 2096 logged certs) — possible misconfiguration or shadow IT. 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 (ns4.apa.net., ns3.apa.at.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.