Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
rapportive.com scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, TLS Configuration, HSTS Header 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 rapportive.com compares
Grade distribution across 2378 companies we've scanned. rapportive.com scores better than 78% 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
rapportive.com — Grade B (85/100)
2378 companies scanned
Security checks
Each check inspects a different part of rapportive.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 8 nameservers configured (dns3.p09.nsone.net., dns4.p09.nsone.net., ns1-42.azure-dns.com., ns2-42.azure-dns.net.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest). Issues: No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-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.
HSTS Header
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Certificate Hygiene
Strengths: Certificate valid, 155 days remaining; Issued by DigiCert Inc.
Recommended actions
3 items
Steps to improve rapportive.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for rapportive.com but has gaps. Actions needed: add SPF record; 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
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Configure DKIM and publish public key in DNS
3
Verify with: nslookup -type=txt _dmarc.rapportive.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 rapportive.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 rapportive.com
3
Add optional security headers (Referrer-Policy, Permissions-Policy)
rapportive.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.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://rapportive.com | 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=reject
Strengths: DMARC policy set to reject (strongest). Issues: No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Missing
No SPF record found.
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 155 days remaining; Issued by DigiCert Inc.
DNSSEC
Not enabled
Strengths: 8 nameservers configured (dns3.p09.nsone.net., dns4.p09.nsone.net., ns1-42.azure-dns.com., ns2-42.azure-dns.net.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.