Skip to main content

Is bit.ly a Scam? Security Check Results - bit.ly Reviews

bit.ly favicon

Is bit.ly Safe? Security Analysis for Bitly Connections Platform | Short URLs, QR Codes, and More

https://bit.ly

Check if bit.ly is a scam or legitimate. Free security scan and reviews.

Analyzed 9/5/2025Completed 1:45:35 AM
64
Security Score
MEDIUM RISK

AI analysis incomplete. Run a Rescan to get comprehensive AI-powered insights including business intelligence, technology detection, and security observations.

🛡️Security Headers

HTTP security headers analysis and recommendations.

Security Headers

HTTP security headers analysis

45/100
Score

Missing X-Content-Type-Options header

MEDIUM

Prevents MIME type sniffing

Missing Content-Security-Policy header

HIGH

Controls resources the browser is allowed to load

Missing X-XSS-Protection header

MEDIUM

Legacy XSS protection (deprecated but still recommended)

Missing Referrer-Policy header

LOW

Controls referrer information sent with requests

Missing Permissions-Policy header

MEDIUM

Controls browser features and APIs

Sensitive data may be cached

LOW

Cache-Control header should include "no-store" for sensitive pages

👤GDPR Compliance

Privacy and data protection assessment under GDPR regulations.

GDPR Compliance

Privacy and data protection assessment

100/100
Score
No issues found

GDPR Compliance Analysis

Privacy Policy85% confidence
Cookie Policy85% confidence
Contact Information Found90% confidence
emailphone

🛡️NIS2 Compliance

Network & Information Security Directive compliance assessment.

NIS2 Compliance

Network & Information Security Directive

17/100
Score

No information security framework found

HIGH

NIS2 requires documented cybersecurity and information security measures

No vulnerability disclosure policy

MEDIUM

NIS2 encourages coordinated vulnerability disclosure

No security policy documentation found

HIGH

NIS2 requires documented cybersecurity governance and risk management

No incident response procedures found

HIGH

NIS2 requires documented incident response and business continuity plans

No business continuity planning found

MEDIUM

NIS2 emphasizes operational resilience and business continuity

No security contact information

HIGH

NIS2 requires clear incident reporting channels

No vulnerability reporting mechanism

MEDIUM

Clear vulnerability reporting supports coordinated disclosure

No NIS2 reference found

LOW

Consider explicitly mentioning NIS2 compliance efforts

📧Email Security

SPF, DKIM, and DMARC validation and email security assessment.

Email Security

SPF, DKIM, and DMARC validation

85/100
Score

Complex SPF record

LOW

Too many include statements can cause lookup limits

DMARC not enforcing

MEDIUM

DMARC policy is set to "none"

SPF
Sender Policy Framework
DKIM
DomainKeys Identified Mail
DMARC
Domain-based Message Authentication
MX Records
Mail Exchange Records
BIMI
Brand Indicators
MTA-STS
Mail Transfer Agent Security
TLS-RPT
TLS Reporting
DNSSEC
DNS Security
SPF Details
Record:
v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com include:_spf1.mailgun.org include:_spf2.mailgun.org exists:%{i}._spf.mta.salesforce.com include:stspg-customer.com include:mail.zendesk.com a:zgateway.zuora .com -all
DNS Lookups:9/10
Policy:-all
DKIM Selectors Found
Selector:google(1296-bit rsa)
DMARC Details
Policy:none
Aggregate Reports:dmarc@bitly.com
Forensic Reports:ruf@dmarc.bitly.net
MTA-STS Details

🏆SSL/TLS Security

Certificate validity and encryption analysis.

SSL/TLS Security

Certificate validity and encryption analysis

77/100
Score

Weak Protocols Supported

HIGH

Server supports weak protocols: TLSv1.1

OCSP Stapling Not Enabled

LOW

OCSP stapling improves performance and privacy

Certificate Transparency Not Implemented

LOW

Certificate is not logged in Certificate Transparency logs

Partial SSL/TLS Assessment

LOW

Completed 3 of 4 security checks due to time constraints

Protocol Support

TLSv1.2TLSv1.3TLSv1.1

OCSP Status

OCSP Stapling Disabled

📊DNS Health

DNS configuration and security assessment.

DNS Health

DNS configuration and security assessment

85/100
Score

DNSSEC Not Enabled

MEDIUM

DNSSEC is not configured for this domain

DMARC Policy Set to None

LOW

DMARC is configured but not enforcing any policy

DNS Records

A Records:67.199.248.14, 67.199.248.15
Name Servers:
ns-1053.awsdns-03.orgDNS only
ns-1689.awsdns-19.co.ukDNS only
ns-343.awsdns-42.comDNS only
ns-880.awsdns-46.netDNS only
ns-cloud-b1.googledomains.comDNS only
ns-cloud-b2.googledomains.comDNS only
ns-cloud-b3.googledomains.comDNS only
ns-cloud-b4.googledomains.comDNS only
MX Records:
10: aspmx.l.google.com
20: alt1.aspmx.l.google.com
20: alt2.aspmx.l.google.com
30: aspmx2.googlemail.com
30: aspmx3.googlemail.com
SOA:Serial: 1, TTL: 300s

DNSSEC Status

DNSSEC Not Enabled

DNS Performance

Resolution Time:41ms

SPF Analysis

SPF Record:
v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com include:_spf1.mailgun.org include:_spf2.mailgun.org exists:%{i}._spf.mta.salesforce.com include:stspg-customer.com include:mail.zendesk.com a:zgateway.zuora .com -all

⚡Network Security

Port scanning and network exposure analysis.

Network Security

Port scanning and network exposure analysis

100/100
Score

Good Network Security Posture

LOW

No unnecessary services detected on common risky ports

Analyze Another Website