Is x.com a scam site? Scam, spam & reviews

Score
96
HTTP status
200
https://x.com/
SSL/TLS
Valid
2026-01-11T19:12:57+00:00
Server/AS
CLOUDFLARENET, US
172.66.0.227
Open site

Scores & key points

Security
Reputation
Scam risk

Overview

Label
X

アメリカのソーシャル・ネットワーキング・サービス

Sources:
Wikidata Wikipedia (English) Wikipedia (Japanese) Wikipedia (Achinese) Wikipedia (Afrikaans) Wikipedia (Albanian) Wikipedia (Amharic)
+164 Show more languages
Wikipedia (Aragonese) Wikipedia (Arabic) Wikipedia (Moroccan Arabic) Wikipedia (Egyptian Arabic) Wikipedia (Assamese) Wikipedia (Asturian) Wikipedia (Avaric) Wikipedia (Awadhi) Wikipedia (Azerbaijani) Wikipedia (azb) Wikipedia (Balinese) Wikipedia (Bavarian) Wikipedia (Bikol) Wikipedia (Belarusian) Wikipedia (Belarusian) Wikipedia (Betawi) Wikipedia (Bulgarian) Wikipedia (Bhojpuri) Wikipedia (Bislama) Wikipedia (Banjar) Wikipedia (blk) Wikipedia (Bambara) Wikipedia (Bangla) Wikipedia (Breton) Wikipedia (Bosnian) Wikipedia (Catalan) Wikipedia (cdo) Wikipedia (Cebuano) Wikipedia (Cherokee) Wikipedia (Central Kurdish) Wikipedia (Czech) Wikipedia (Chuvash) Wikipedia (Welsh) Wikipedia (Danish) Wikipedia (German) Wikipedia (Dinka) Wikipedia (Zaza) Wikipedia (dty) Wikipedia (Greek) Wikipedia (Esperanto) Wikipedia (Spanish) Wikipedia (Estonian) Wikipedia (Basque) Wikipedia (Persian) Wikipedia (Finnish) Wikipedia (Faroese) Wikipedia (French) Wikipedia (Arpitan) Wikipedia (Western Frisian) Wikipedia (Irish) Wikipedia (Scottish Gaelic) Wikipedia (Galician) Wikipedia (Gilaki) Wikipedia (Guarani) Wikipedia (Goan Konkani) Wikipedia (Gujarati) Wikipedia (Manx) Wikipedia (Hausa) Wikipedia (Hakka Chinese) Wikipedia (Hebrew) Wikipedia (Hindi) Wikipedia (Fiji Hindi) Wikipedia (Croatian) Wikipedia (Hungarian) Wikipedia (Armenian) Wikipedia (Interlingua) Wikipedia (Indonesian) Wikipedia (Interlingue) Wikipedia (Iloko) Wikipedia (Ido) Wikipedia (Icelandic) Wikipedia (Italian) Wikipedia (Javanese) Wikipedia (Georgian) Wikipedia (Kara-Kalpak) Wikipedia (kbp) Wikipedia (Kazakh) Wikipedia (Khmer) Wikipedia (Kannada) Wikipedia (Korean) Wikipedia (Kashmiri) Wikipedia (Kurdish) Wikipedia (Kyrgyz) Wikipedia (Latin) Wikipedia (Luxembourgish) Wikipedia (Limburgish) Wikipedia (Lombard) Wikipedia (Lao) Wikipedia (Lithuanian) Wikipedia (Latvian) Wikipedia (Madurese) Wikipedia (Maithili) Wikipedia (Malagasy) Wikipedia (Minangkabau) Wikipedia (Macedonian) Wikipedia (Malayalam) Wikipedia (Mongolian) Wikipedia (Manipuri) Wikipedia (Marathi) Wikipedia (Malay) Wikipedia (Burmese) Wikipedia (Erzya) Wikipedia (Mazanderani) Wikipedia (Low German) Wikipedia (Nepali) Wikipedia (Nias) Wikipedia (Dutch) Wikipedia (Norwegian Nynorsk) Wikipedia (Norwegian) Wikipedia (Nyanja) Wikipedia (Occitan) Wikipedia (Odia) Wikipedia (Punjabi) Wikipedia (Polish) Wikipedia (Western Panjabi) Wikipedia (Pashto) Wikipedia (Portuguese) Wikipedia (Quechua) Wikipedia (Romanian) Wikipedia (Russian) Wikipedia (Sanskrit) Wikipedia (Yakut) Wikipedia (Santali) Wikipedia (Sicilian) Wikipedia (Scots) Wikipedia (Sindhi) Wikipedia (Serbo-Croatian) Wikipedia (Shan) Wikipedia (Sinhala) Wikipedia (English) Wikipedia (Slovak) Wikipedia (Slovenian) Wikipedia (Somali) Wikipedia (Albanian) Wikipedia (Serbian) Wikipedia (Sundanese) Wikipedia (Swedish) Wikipedia (Swahili) Wikipedia (syl) Wikipedia (Tamil) Wikipedia (Telugu) Wikipedia (Tajik) Wikipedia (Thai) Wikipedia (Turkmen) Wikipedia (Tagalog) Wikipedia (Turkish) Wikipedia (Tatar) Wikipedia (Uyghur) Wikipedia (Ukrainian) Wikipedia (Urdu) Wikipedia (Uzbek) Wikipedia (Venetian) Wikipedia (Veps) Wikipedia (Vietnamese) Wikipedia (Waray) Wikipedia (Wu Chinese) Wikipedia (Mingrelian) Wikipedia (Yiddish) Wikipedia (Yoruba) Wikipedia (Zeelandic) Wikipedia (Chinese) Wikipedia (Chinese) Wikipedia (Min Nan Chinese) Wikipedia (Chinese)

Caution signals

  • [Low] Cookie security attributes are insufficient (total 1).

Reputation

Open PageRank 9.49 / 10
Tranco 69 Global
Source: top-1m.csv

Review summary — x.com

Overall 96 (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
  • Domain age ≥ 1 year

Weaknesses

Detailed review — x.com

Domain review

Domain created: 1993-04-02T05:00:00Z (≈ 32y 8m). Registrar: GoDaddy.com, LLC. Hosting / AS: CLOUDFLARENET, US. Popularity: Tranco #69, OPR 9.49/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC reject. Certificate valid until: 2026-01-11T19:12:57+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 CLOUDFLARENET, 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://x.com/.well-known/security.txt). Missing cookie attributes: Secure×0 / HttpOnly×0 / SameSite×1. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

Age: about (≈ 32y 8m) (created on 1993-04-02T05:00:00Z).

GSB clean

WebRisk clean

Certificate valid until: 2026-01-11T19:12:57+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.

Cookies without Secure / HttpOnly / SameSite can be vulnerable to theft or session fixation attacks.

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

Estimated domain age
32y 8m
Registrar
GoDaddy.com, LLC
SSL valid
Yes
SSL expires
2026-01-11T19:12:57+00:00
HTTP status
200
Server / ASN
CLOUDFLARENET, US
Final URL
https://x.com/
SPF
Yes
DMARC
Yes
CT wildcard usage
No
HSTS preload
Unknown
security.txt
Yes
TLS‑RPT receivers
Absent
Domain creation date
1993-04-02T05:00:00Z
Hosting / AS
CLOUDFLARENET
GSB status
No match
WebRisk status
No match
DMARC policy
reject
PSI mobile
41
PSI desktop
43
DNSSEC
Absent
Legal/contact pages
No
Structured data: Organization
Absent
Structured data: contactPoint
Absent
Registry risk (0–100)
3
dmarc_p
reject
dmarc_rua
mailto:caf935f12c8645b2921b0749d1fcd49e@dmarc-reports.cloudflare.net
mixed_http
0
cookie_no_secure
0
cookie_no_httponly
0
cookie_no_samesite
1
JS obfuscation score
0
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-11-24 00:09:00
Email

Traffic signals

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

Performance

Field LCP8841ms
Field INP-ms
Field CLS9
Lab LCP16360ms
Lab TBT1571ms
Mobile score41
Lab LCP3668ms
Lab TBT1201ms
Desktop score43
https://x.com/

Security headers

  • HSTS
  • Content‑Security‑Policy
  • X‑Content‑Type‑Options
  • X‑Frame‑Options
  • Referrer‑Policy
  • Permissions‑Policy
Set Referrer‑Policy
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
Set Permissions‑Policy
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
Add security attributes to cookies
Set-Cookie: name=value; Path=/; Secure; HttpOnly; SameSite=Lax
Examples: __cf_bm=A6Ad37R33N6uG2r4Fxqd8QtKLSjyumdoCS6Q5MAw2bc-1763942895.317636-1.0.1.1-q.3zAAPobs2GXRWXhy2WNCB29Z6ljx9xIN3E4mXMuazeR81ahJwbtVbFEysGPqCpJxbLzAkY9ZntEHpPWQmuFutESVhYYdhB._LBMafqpb05FN0b.X5soDVBD3agUtJg

Domain lineage

  1. 1993-04-02
    Domain registered: 1993-04-02T05:00:00Z

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB 0%
SPF Configured
DMARC Configured
DNSSEC No
Cookie security SameSite×1
Mixed content (http) 0
Legal pages Absent
DMARC details
DMARC policy (p): reject
Aggregate reports (rua): mailto:caf935f12c8645b2921b0749d1fcd49e@dmarc-reports.cloudflare.net
TXT: v=DMARC1; p=reject; rua=mailto:caf935f12c8645b2921b0749d1fcd49e@dmarc-reports.cloudflare.netv=DMARC1; p=reject; rua=mailto:caf935f12c8645b2921b0749d1fcd49e@dmarc-reports.cloudflare.net
HTTP status200
Server CLOUDFLARENET, US
CDN / Hosting Cloudflare CDN
HSTSNo
Valid until2026-01-11T19:12:57+00:00
IssuerLet's Encrypt / E7
Registrant / organizationCLOUDFLARENET, US
RegistrarGoDaddy.com, LLC
ASN13335
Network172.64.0.0/13
TitleX. It’s what’s happening / X
Final URL: https://x.com/

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 10/100)
  • Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.

For session/login cookies, always set Secure, HttpOnly, and SameSite.

HTTP status (deep) 200
Set‑Cookie (count) 3
Cookie security insufficient Secure×0 / HttpOnly×2 / SameSite×1
HTTP resources (deep) 0
Top third‑party hosts 2
Collection time: 2025-11-24T00:09:00+00:00
abs.twimg.com abs-0.twimg.com
Set‑Cookie (samples)
guest_id=v1%3A176394294055148394; SameSite=None; Secure; Path=/; Domain=.x.com; Max-Age=34214400; Expires=Fri, 25 Dec 2026 00:09:00 GMT</code><br><code>ct0=; SameSite=Lax; Secure; Path=/; Domain=.x.com; Max-Age=0; Expires=Thu, 01 Jan 1970 00:00:01 GMT</code><br><code>__cf_bm=x6oMnmr4C6i31fWx4vbOSkaQ5yPL5mUIuTggf_kNCL4-1763942940.4811962-1.0.1.1-z37utOHWP6QuquDiMvRqwVaMYZ5RF7TfWubHTjxYl0LbTbbdKr6d8tPe6sVjdLSHgppBrvCbnc6E0H4OP9s0rOzhdzCpGd_gYJwuqnJRjVb5ew4qToJ7mcQTQYIYAzVo; HttpOnly; Secure; Path=/; Domain=x.com; Expires=Mon, 24 Nov 2025 00:39:00 GMT

Social

  • X

Platforms that this site may be using.

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. Missing cookie security attributes or cross-domain POST forms can make sessions easier to steal or misuse. After logging in, watch for unusual account or billing activity.

Server location

- (-) · ASN 13335 / CLOUDFLARENET

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum 3e8e1053f31ba9b5f2412a6038a5ed003d9034971cec92b2213233dfa293df72

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