Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
tpaga.co scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: HSTS Header. Positive signals: Known Breaches, TLS Configuration, DMARC / Email Security 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 tpaga.co compares
Grade distribution across 2378 companies we've scanned. tpaga.co scores better than 72% 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
tpaga.co — Grade B- (82/100)
2378 companies scanned
Security checks
Each check inspects a different part of tpaga.co'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.
DNS Configuration
Strengths: 4 nameservers configured (ns-899.awsdns-48.net., ns-96.awsdns-12.com., ns-1241.awsdns-27.org., ns-1797.awsdns-32.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Security Headers
3/5 security headers present. Missing: CSP, Referrer-Policy.
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.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; DKIM configured (selectors: google, k1). Issues: SPF record uses neutral (?all) — no real enforcement.
Certificate Hygiene
Strengths: Certificate valid, 31 days remaining; Issued by Let's Encrypt.
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
3 items
Steps to improve tpaga.co's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on tpaga.co. 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://tpaga.co | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
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 tpaga.co 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 .co TLD
4
Verify: dig +dnssec tpaga.co
3
Add optional security headers (CSP, Referrer-Policy)
tpaga.co has most security headers configured. Missing: CSP, Referrer-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: Referrer-Policy: strict-origin-when-cross-origin
3
Verify with: curl -sI https://tpaga.co | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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; DKIM configured (selectors: google, k1). Issues: SPF record uses neutral (?all) — no real enforcement.
SPF Record
Present
v=spf1 include:mail.zendesk.com include:_spf.google.com include:spf.mailjet.com include:amazonses.co
Security Headers
3/5 present
Missing: CSP, Referrer-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, 31 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-899.awsdns-48.net., ns-96.awsdns-12.com., ns-1241.awsdns-27.org., ns-1797.awsdns-32.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.