Overview
Findings
Actions
Details
Related
C-
72 / 100

nuvola.tech

Security report · Scanned February 18, 2026

Checks
8
Passed
5
Warnings
1
Critical
2
AI-Generated Summary
What this means

nuvola.tech 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 nuvola.tech compares

Grade distribution across 2378 companies we've scanned. nuvola.tech scores better than 47% of them.

47th percentile
0 Percentile rank 100
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
nuvola.tech — Grade C- (72/100) 2378 companies scanned
Security checks

Each check inspects a different part of nuvola.tech'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.
Problem
Security Headers
Only 0/5 security headers 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.
Problem
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.
Needs work
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
CVE Exposure
Detected technologies: cloudflare, WP Engine. (cloudflare detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Healthy
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-d3.googledomains.com., ns-cloud-d2.googledomains.com., ns-cloud-d1.googledomains.com., ns-cloud-d4.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
Certificate Hygiene
Strengths: Certificate valid, 40 days remaining; Issued by Let's Encrypt.
Healthy
Recommended actions
3 items

Steps to improve nuvola.tech's security grade, ranked by impact.

1
Enable HSTS (HTTP Strict Transport Security)
Impact: < 1 Hour
HIGH
The HSTS header is missing on nuvola.tech. 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://nuvola.tech | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
2
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
Impact: 1–2 Hours
HIGH
5 of 5 recommended security headers are missing on nuvola.tech: 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 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
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://nuvola.tech | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Strengthen email authentication configuration
Impact: 2–4 Hours
HIGH
Email authentication is partially configured for nuvola.tech 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.nuvola.tech
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
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, 40 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-d3.googledomains.com., ns-cloud-d2.googledomains.com., ns-cloud-d1.googledomains.com., ns-cloud-d4.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.