Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
sigmagenetics.com scored 72/100, meeting baseline requirements but with 1 finding that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header, Security Headers. Positive signals: Known Breaches, TLS Configuration, DNS Configuration all passed.
3 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 sigmagenetics.com compares
Grade distribution across 2378 companies we've scanned. sigmagenetics.com scores better than 47% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
sigmagenetics.com — Grade C- (72/100)
2378 companies scanned
Security checks
Each check inspects a different part of sigmagenetics.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
Only 1/5 security headers present. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 2 nameservers configured (dns2.registrar-servers.com., dns1.registrar-servers.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
CVE Exposure
Detected technologies: nginx/1.27.2. No high or critical CVEs found for detected versions.
Certificate Hygiene
Strengths: Certificate valid, 88 days remaining; Issued by Let's Encrypt.
Recommended actions
3 items
Steps to improve sigmagenetics.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for sigmagenetics.com but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. 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
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.sigmagenetics.com
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 HSTS (HTTP Strict Transport Security)
The HSTS header is missing on sigmagenetics.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://sigmagenetics.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
3
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy)
4 of 5 recommended security headers are missing on sigmagenetics.com: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-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 Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Content-Type-Options: nosniff
3
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Verify with: curl -sI https://sigmagenetics.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
Not configured
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 include:_spf.google.com ~all
Security Headers
1/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-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, 88 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 2 nameservers configured (dns2.registrar-servers.com., dns1.registrar-servers.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.