Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
nanonets.com scored 78/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: DNS Configuration, Known Breaches, HSTS Header 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 nanonets.com compares
Grade distribution across 2378 companies we've scanned. nanonets.com scores better than 59% 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
nanonets.com — Grade C+ (78/100)
2378 companies scanned
Security checks
Each check inspects a different part of nanonets.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 1/5 security headers present. Missing: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-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, s1, s2, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).
Certificate Hygiene
Strengths: Certificate valid, 340 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 4 nameservers configured (ns-1048.awsdns-03.org., ns-1593.awsdns-07.co.uk., ns-262.awsdns-32.com., ns-870.awsdns-44.net.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
CVE Exposure
Detected technologies: cloudflare, Proxy/CDN. (cloudflare, Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Recommended actions
3 items
Steps to improve nanonets.com's security grade, ranked by impact.
1
Add missing security headers (X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
4 of 5 recommended security headers are missing on nanonets.com: 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: X-Content-Type-Options: nosniff
2
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://nanonets.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
Strengthen email authentication configuration
Email authentication is partially configured for nanonets.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.nanonets.com
3
Review certificate configuration
Certificate issues found for nanonets.com: 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.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 a mx include:_spf.google.com include:sendgrid.net include:mail.zendesk.com include:amazonses.
Security Headers
1/5 present
Missing: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 340 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-1048.awsdns-03.org., ns-1593.awsdns-07.co.uk., ns-262.awsdns-32.com., ns-870.awsdns-44.net.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.