Why This Rejection Happens
The Privacy Policy URL you provided is insecure (HTTP instead of HTTPS), or the SSL certificate is expired/invalid. Carriers require secure connections for data policies.
Root Cause Analysis
The Fix
Install a valid SSL certificate on your website and ensure the URL starts with https://.
✓ Secure URL
https://www.mybrand.com/privacy
✗ Insecure URL
http://www.mybrand.com/privacy
Related Rejection Codes
Secure Your Policy
Get an automatically secured (HTTPS) privacy page hosted by us.
Comprehensive TCR rejection remediation powered by MyTCRPlus.com
What reviewers check for code 7105
Code 7105 is reported as "Privacy Policy SSL Failed". The privacy policy URL must load over a valid HTTPS certificate. Reviewers and automated checkers treat an expired, self-signed, mismatched or missing certificate as a failed policy, because consumers following the link would see a browser security warning instead of the policy.
Where code 7105 comes from
Code 7105 is a campaign review reason code used to report a specific deficiency found during manual campaign vetting. CSPs surface it in the rejection notice alongside any other codes found in the same review, so check for companion codes before resubmitting. It is marked High severity: it blocks approval, but it is fully fixable by correcting the submission and resubmitting.
Fix and verify before resubmitting
- Test the URL in an SSL checker and confirm the certificate is valid, unexpired and issued for the exact hostname (including or excluding www).
- Renew or reissue the certificate through your host or a free provider such as Let's Encrypt, and enable auto-renewal.
- Redirect http:// to https:// and fix mixed-content warnings on the policy page.
- Confirm the full certificate chain is installed; missing intermediates fail on some validators even when browsers show a padlock.
- Update the campaign with the https:// URL and resubmit.
- Resubmit with a note that references code 7105 (Privacy Policy SSL Failed) and lists each change made.
Sample resubmission note
Many CSPs let you add a note for the reviewer when you resubmit. A short, specific note shows what changed and speeds up the second review. Example for Northline Heating & Air:
Northline Heating & Air corrected the deficiency reported as code 7105 (Privacy Policy SSL Failed). Changes made: test the URL in an SSL checker and confirm the certificate is valid, unexpired and issued for the exact hostname (including or excluding www); renew or reissue the certificate through your host or a free provider such as Let's Encrypt, and enable auto-renewal; redirect http:// to https:// and fix mixed-content warnings on the policy page. All URLs, keywords and auto-replies were re-tested from an external network before this resubmission, and the campaign text now matches the live opt-in exactly.
Common mistakes that keep code 7105 coming back
- Installing a certificate for the root domain while the policy lives on www (or the reverse).
- Letting a certificate auto-renewal fail silently between submission and review.
- Linking the http:// version of the policy in the campaign.
Related rejection codes
- Code 7013: Privacy Policy SSL Failed
- Code 2131: Verbal Script Missing STOP Instructions
- Code 2128: Opt-in Form Missing HELP Instructions
- Code 2127: Verbal Script Missing STOP Instructions
- Code 2126: Opt-in Form Missing STOP Instructions
- Code 2124: Verbal Script Missing Frequency Disclosure
Frequently asked questions about code 7105
My browser shows a padlock. Why did I still get code 7105?
Browsers fill in missing intermediate certificates from cache; validators do not. Run an external SSL test and install the full chain.
Do I need to change anything else after fixing the certificate?
Check that the opt-in page, SMS terms and website also load over valid HTTPS, since reviewers test every URL in the campaign.