72
Conditional

capitaland.com

Security posture assessment · Scanned February 15, 2026

Findings
4 · 3 · 1
Checks
8 passive

capitaland.com scored 72/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.

Critical gaps in: DMARC / Email Security. Positive signals: Known Breaches, TLS Configuration, HSTS Header all passed.

4 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.

Ordered by priority · 4 items
1
Set up email authentication (SPF)
Effort: 1–2 days   Owner: IT / DNS administrator
critical
Without email authentication, anyone can send emails that appear to come from capitaland.com. This is the most common vector for phishing attacks targeting employees and customers. SPF is not configured.
Compliance Impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
Remediation Steps
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@capitaland.com
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
2
Enable DNSSEC on your domain
Effort: 1–3 days (depends on registrar)   Owner: DNS administrator / domain registrar
medium
Without DNSSEC, DNS responses for capitaland.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
Remediation Steps
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 capitaland.com
3
Review certificate configuration — expires in 23 days
Effort: 1–2 hours   Owner: Infrastructure / DevOps
medium
Certificate issues found for capitaland.com: certificate expires in 23 days. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
Remediation Steps
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consolidate certificate issuance to 1–2 trusted CAs
4
Add optional security headers (Referrer-Policy, Permissions-Policy)
Effort: < 1 hour   Owner: Web server administrator
low
capitaland.com has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
Remediation Steps
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://capitaland.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
DMARC / Email Security
Critical
DNS Configuration
Warning
Security Headers
Warning
Certificate Hygiene
Warning
Known Breaches
Healthy
TLS Configuration
Healthy
HSTS Header
Healthy
CVE Exposure
Healthy