Overview
Findings
Actions
Details
Related
B+
88 / 100

fullstackacademy.com

Security report · Scanned February 18, 2026

Checks
8
Passed
5
Warnings
3
Critical
0
AI-Generated Summary
What this means

fullstackacademy.com scored 88/100, demonstrating a strong security posture. Minor improvements are noted below.

Positive signals: Known Breaches, DMARC / Email Security, TLS 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 fullstackacademy.com compares

Grade distribution across 2378 companies we've scanned. fullstackacademy.com scores better than 81% of them.

81th 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
fullstackacademy.com — Grade B+ (88/100) 2378 companies scanned
Security checks

Each check inspects a different part of fullstackacademy.com's public security setup. Green means healthy, yellow needs attention, red is a problem.

DNS Configuration
Strengths: 4 nameservers configured (ns-1055.awsdns-03.org., ns-135.awsdns-16.com., ns-1985.awsdns-56.co.uk., ns-840.awsdns-41.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Needs work
Security Headers
3/5 security headers present. Missing: X-Frame-Options, Permissions-Policy.
Needs work
Certificate Hygiene
Strengths: Certificate valid, 152 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
Needs work
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, smtpapi).
Healthy
HSTS Header
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
Healthy
CVE Exposure
Detected technologies: nginx, Blitz, Proxy/CDN, SEOmatic. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Healthy
Recommended actions
3 items

Steps to improve fullstackacademy.com's security grade, ranked by impact.

1
Enable DNSSEC on your domain
Impact: 1–3 Days (Depends On Registrar)
MEDIUM
Without DNSSEC, DNS responses for fullstackacademy.com 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 .com TLD
4
Verify: dig +dnssec fullstackacademy.com
2
Add optional security headers (X-Frame-Options, Permissions-Policy)
Impact: < 1 Hour
LOW
fullstackacademy.com has most security headers configured. Missing: X-Frame-Options, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://fullstackacademy.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Review certificate configuration
Impact: 1–2 Hours
LOW
Certificate issues found for fullstackacademy.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=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, smtpapi).
SPF Record
Present
v=spf1 include:_spf.google.com include:_spf.mailgun.org include:_spf.eu.mailgun.org include:2972642.
Security Headers
3/5 present
Missing: X-Frame-Options, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 152 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1055.awsdns-03.org., ns-135.awsdns-16.com., ns-1985.awsdns-56.co.uk., ns-840.awsdns-41.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.