Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
pennyapp.io scored 90/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, TLS Configuration, HSTS Header all passed.
2 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 pennyapp.io compares
Grade distribution across 2598 companies we've scanned. pennyapp.io scores better than 89% of them.
83
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
pennyapp.io — Grade A- (90/100)
2598 companies scanned
Security checks
Each check inspects a different part of pennyapp.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: mandrill). Issues: No DMARC record found — email spoofing is not prevented.
DNS Configuration
Strengths: 4 nameservers configured (ns-1884.awsdns-43.co.uk., ns-510.awsdns-63.com., ns-632.awsdns-15.net., ns-1240.awsdns-27.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
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: AmazonS3, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 372 days remaining; Issued by Amazon.
Recommended actions
2 items
Steps to improve pennyapp.io's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for pennyapp.io 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.pennyapp.io
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 pennyapp.io 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 .io TLD
4
Verify: dig +dnssec pennyapp.io
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
Not configured
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: mandrill). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 include:enchanthq.net include:spf.mandrillapp.com ~all
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 372 days remaining; Issued by Amazon.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1884.awsdns-43.co.uk., ns-510.awsdns-63.com., ns-632.awsdns-15.net., ns-1240.awsdns-27.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.