Is linktr.ee a scam site? Scam, spam & reviews

Score
87
HTTP status
200
https://linktr.ee/
SSL/TLS
Valid
2026-01-31T06:13:25+00:00
Server/AS
FASTLY, US
151.101.2.133
Open site

Scores & key points

Security
Reputation
Scam risk

Overview

Label
Linktree

australischer Social-Media-Landingpage-Dienst

Caution signals

No clear warnings detected.

Reputation

Open PageRank 7.55 / 10
Tranco 252 Global
Source: sqlite

Review summary — linktr.ee

Overall 87 (Mostly safe)

Multiple security indicators are favorable and there are few major risk signals.

Strengths

  • Valid SSL/TLS certificate
  • HSTS enabled
  • CSP enabled
  • SPF configured
  • DMARC configured

Weaknesses

Detailed review — linktr.ee

Domain review

Hosting / AS: FASTLY, US — United States. Popularity: Tranco #252, OPR 7.55/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC reject. Certificate valid until: 2026-01-31T06:13:25+00:00.

Shop / transaction review

No mixed content detected. No mixed content detected. Structured data: Organization Absent, contactPoint Absent. Hidden text ratio 0%.

Technical review

HTTP 200 Success · Server FASTLY, US. HSTS Off (preload: Unknown). Applies 4/6 security headers. DNSSEC Off. Email security: SPF On, DMARC reject. MTA‑STS policy: None. TLS‑RPT Off. security.txt: available (https://linktr.ee/security.txt). JS obfuscation score 10. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

GSB clean

WebRisk clean

Certificate valid until: 2026-01-31T06:13:25+00:00.

Email security: SPF On, DMARC reject.

Applies 4/6 security headers.

No mixed content detected.

Looking at operator information together with trust metrics helps you judge brand/merchant consistency and the likelihood of long‑term operation.

Checking payment page security (HTTPS enforcement, form target host consistency, script integrity) along with customer support and return policy gives a more accurate sense of real‑world trust.

In parallel, applying security headers, automated certificate renewal, email domain protection (DMARC/TLS‑RPT), and removing mixed content will improve overall reliability and delivery/search stability.

Explanation — risks and areas to improve

Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.

Without DNSSEC, trust relies solely on parent name servers and DNS tampering risks can be higher in some environments.

Without MTA‑STS, SMTP TLS enforcement is weaker.

Without TLS‑RPT, it is harder to collect TLS failure signals and operational insight.

Looking at operator information together with trust metrics helps you judge brand/merchant consistency and the likelihood of long‑term operation.

Checking payment page security (HTTPS enforcement, form target host consistency, script integrity) along with customer support and return policy gives a more accurate sense of real‑world trust.

SSL valid
Yes
SSL expires
2026-01-31T06:13:25+00:00
HTTP status
200
Server / ASN
FASTLY, US
Final URL
https://linktr.ee/
SPF
Yes
DMARC
Yes
CT wildcard usage
No
HSTS preload
Unknown
security.txt
Yes
TLS‑RPT receivers
Absent
Hosting / AS
FASTLY
Hosting country
United States
GSB status
No match
WebRisk status
No match
DMARC policy
reject
DNSSEC
Absent
Legal/contact pages
Yes
Structured data: Organization
Absent
Structured data: contactPoint
Absent
Registry risk (0–100)
5
dmarc_p
reject
dmarc_rua
mailto:dmarc_agg@dmarc.everest.email,mailto:dmarc@linktr.ee
mixed_http
0
Platform fingerprint
wordpress
JS obfuscation score
10
Payment logo count
0
Hidden text ratio (%)
0
Cross‑domain POST form count
0
External host logos/icons
0
YARA matches
0

This analysis is an automated, data‑based opinion for reference only. Please verify the information yourself before paying or downloading anything.

About this report

  • First analysis: -
  • Last updated: 2025-12-31 07:20:23
Email

Traffic signals

UTM source -
UTM medium -
ref / from -
Shortened URLs on page 0

Security headers

  • HSTS
  • Content‑Security‑Policy
  • X‑Content‑Type‑Options
  • X‑Frame‑Options
  • Referrer‑Policy
  • Permissions‑Policy
Prevent content type sniffing
add_header X-Content-Type-Options "nosniff" always;
Set Permissions‑Policy
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB 0%
SPF Configured
DMARC Configured
DNSSEC No
Cookie security Absent
Mixed content (http) 0
Legal pages Present
DMARC details
DMARC policy (p): reject
Aggregate reports (rua): mailto:dmarc_agg@dmarc.everest.email,mailto:dmarc@linktr.ee
TXT: v=DMARC1; p=reject; rua=mailto:dmarc_agg@dmarc.everest.email,mailto:dmarc@linktr.ee;v=DMARC1; p=reject; rua=mailto:dmarc_agg@dmarc.everest.email,mailto:dmarc@linktr.ee;
HTTP status200
Server FASTLY, US
CDN / Hosting Fastly CDN
HSTSNo
Valid until2026-01-31T06:13:25+00:00
IssuerLet's Encrypt / R13
Registrant / organizationFASTLY, US
Registrar-
ASN54113
Network151.101.0.0/16
TitleLink in bio tool: Everything you are, in one simple link | Linktree
Final URL: https://linktr.ee/

Threat insight

Mostly safe (risk 0/100)
  • Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.

The risk score of this site is calculated by combining browser security headers, SSL status, mixed content, email domain protection (SPF/DMARC), redirect/obfuscation patterns, and the results of Google Safe Browsing and WebRisk. There are currently few clear signs of malicious behavior, but insufficient security headers or email protection can increase the risk of phishing or man‑in‑the‑middle attacks. Before entering important information, re‑check the domain spelling and how you reached the site (ads, DMs, shortened URLs, etc.). Before entering payment or personal information, verify operator information (company/contact), HTTPS enforcement, DMARC/TLS‑RPT, and check for mixed content.

Deep scan (HTML / headers)

Mostly safe (deep 6/100)
  • The site heavily relies on third‑party resources.

Before entering payment or personal information, verify the site operator/contact, HTTPS enforcement (HSTS), and the presence of DMARC and TLS‑RPT.

HTTP status (deep) 200
Set‑Cookie (count) 0
Cookie security insufficient Secure×0 / HttpOnly×0 / SameSite×0
HTTP resources (deep) 0
Top third‑party hosts 10
Collection time: 2025-12-31T07:20:23+00:00
cdn.prod.website-files.com assets.production.linktr.ee cdn.jsdelivr.net api.consentjs.datagrail.io fonts.googleapis.com fonts.gstatic.com ajax.googleapis.com linktr.ee edge.browser-fp.production.linktr.ee d3e54v103j8qbb.cloudfront.net
Iframe hosts
googletagmanager.com

User scenarios

If you make a payment on this site

No strong malicious signs were found, but online payments always carry some risk. Double-check the amount, payee and refund policy before you pay.

If you log in or enter personal data

No clear malicious patterns were found, but treat passwords and 2FA codes as highly sensitive. Avoid reusing passwords across sites.

Server location

United States (US) · ASN 54113 / FASTLY

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum 37ea47f43e0381c6df758abc861fe7462da0238a0f602a3592be5ef13ed4aceb

Analyzing

Collecting various signals and public data.

  1. Start
  2. Fetch DNS / WHOIS
  3. Check HTTP response
  4. Verify SSL/TLS
  5. Query reputation
  6. Collect PageSpeed data
  7. Analyze security headers
  8. Check email security
  9. Integrate extended signals
  10. Build report