Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
instagram.com scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Cookie Security. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support 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 instagram.com compares
Grade distribution across 2598 companies we've scanned. instagram.com scores better than 78% 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
instagram.com — Grade B (85/100)
2598 companies scanned
Security checks
Each check inspects a different part of instagram.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Cookie Security
Strengths: 2 cookie(s) analyzed; All cookies have Secure flag. Issues: 1/2 cookie(s) missing HttpOnly flag (csrftoken); 2/2 cookie(s) missing SameSite attribute (csrftoken, mid).
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
Strengths: CAA records configured (1 record(s)); Authorized CAs: digicert.com; account=271b0beda0771d006aa3a6c11b05187d456d6c239b46cb5241196095b09c92af. Issues: No iodef record — CA violations won't be reported to the domain owner.
DNS Configuration
Strengths: 4 nameservers configured (b.ns.instagram.com., a.ns.instagram.com., d.ns.instagram.com., c.ns.instagram.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Known Breaches
1 breach(es) found (1 verified). Total accounts affected: 6,215,150. Breaches: Instagram (2026-01-07, 6,215,150 accounts).
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
Certificate Hygiene
Strengths: Issued by DigiCert Inc. Issues: Certificate expires in 7 days — critical, renew immediately. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
MX Records & Mail Provider
Strengths: Mail handled by Proofpoint; 2 MX record(s) configured; Multiple MX records provide redundancy; Equal-priority MX records (10) — standard round-robin load balancing for Proofpoint.
TLS Configuration
TLSv1.3 negotiated with TLS_CHACHA20_POLY1305_SHA256 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: smtpapi).
HSTS Header
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
4/5 security headers present. Missing: Referrer-Policy.
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.
Recommended actions
3 items
Steps to improve instagram.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for instagram.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 instagram.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
Review unverified breach disclosure
instagram.com appears in an unverified breach report. This may be a false positive or data aggregation error. Investigate to confirm or rule out exposure.
How to fix this
1
Review the breach details on haveibeenpwned.com
2
Cross-reference with internal incident records
3
If confirmed, follow breach response procedures
3
Review certificate configuration — expires in 7 days
Certificate issues found for instagram.com: certificate expires in 7 days; wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
How to fix this
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
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_CHACHA20_POLY1305_SHA256 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: smtpapi).
SPF Record
Present
v=spf1 include:facebookmail.com include:_spf.fb.com -all
Security Headers
4/5 present
Missing: Referrer-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Issued by DigiCert Inc. Issues: Certificate expires in 7 days — critical, renew immediately. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (b.ns.instagram.com., a.ns.instagram.com., d.ns.instagram.com., c.ns.instagram.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.