Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
makeschool.com scored 75/100, meeting baseline requirements but with 5 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, TLS Configuration, CVE Exposure all passed.
5 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 makeschool.com compares
Grade distribution across 2378 companies we've scanned. makeschool.com scores better than 55% 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
makeschool.com — Grade C (75/100)
2378 companies scanned
Security checks
Each check inspects a different part of makeschool.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 2 nameservers configured (pat.ns.cloudflare.com., kip.ns.cloudflare.com.); 5 MX records present; 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).
HSTS Header
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
Certificate Hygiene
Strengths: Certificate valid, 64 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
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: cloudflare, Gatsby/3.8.0. (cloudflare detected but excluded from CVE matching — upstream infrastructure). No high or critical CVEs found for detected versions.
Recommended actions
5 items
Steps to improve makeschool.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for makeschool.com 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.makeschool.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 DNSSEC on your domain
Without DNSSEC, DNS responses for makeschool.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 makeschool.com
3
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://makeschool.com | grep -i strict
4
Add optional security headers (CSP, Permissions-Policy)
makeschool.com has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://makeschool.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
5
Review certificate configuration
Certificate issues found for makeschool.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_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:_spf.google.com include:technolutions.net include:mailgun.us include:_spfprod.ngpvan.
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Certificate valid, 64 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (pat.ns.cloudflare.com., kip.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.