Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
opengwas.io scored 70/100, meeting baseline requirements but with 5 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header, Security Headers. Positive signals: MX Records & Mail Provider, TLS Configuration, 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 opengwas.io compares
Grade distribution across 2522 companies we've scanned. opengwas.io scores better than 42% of them.
79
A+
25
A
183
A-
191
B+
72
B
353
B-
121
C+
116
C
324
C-
117
D+
94
D
241
D-
606
F
opengwas.io — Grade C- (70/100)
2522 companies scanned
Security checks
Each check inspects a different part of opengwas.io'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.
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: 4 nameservers configured (ns3.p201.dns.oraclecloud.net., ns1.p201.dns.oraclecloud.net., ns2.p201.dns.oraclecloud.net., ns4.p201.dns.oraclecloud.net.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
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.
MX Records & Mail Provider
No MX records found. This domain does not receive email directly — this is intentional for many domains and carries no security risk. If email is expected, verify mail routing via A/AAAA fallback or a mail provider.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
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.
CVE Exposure
Detected technologies: openresty. No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 60 days remaining; Issued by Let's Encrypt; 98 certificates logged in CT.
Recommended actions
4 items
Steps to improve opengwas.io's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on opengwas.io. 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://opengwas.io | 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 opengwas.io: 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://opengwas.io | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Strengthen email authentication configuration
Email authentication is partially configured for opengwas.io but has gaps. Actions needed: configure DKIM. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Configure DKIM and publish public key in DNS
2
Verify with: nslookup -type=txt _dmarc.opengwas.io
4
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for opengwas.io 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 .io TLD
4
Verify: dig +dnssec opengwas.io
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 soft-fail (~all). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 include:rp.oracleemaildelivery.com include:ap.rp.oracleemaildelivery.com include:eu.rp.oracle
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, 60 days remaining; Issued by Let's Encrypt; 98 certificates logged in CT.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns3.p201.dns.oraclecloud.net., ns1.p201.dns.oraclecloud.net., ns2.p201.dns.oraclecloud.net., ns4.p201.dns.oraclecloud.net.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.