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

Score
85
HTTP status
301
https://docker.com/
SSL/TLS
Valid
2026-01-01T12:43:09+00:00
Server/AS
FASTLY, US
2620:12a:8000::4
Open site

Scores & key points

Security
Reputation
Scam risk

Caution signals

No clear warnings detected.

Reputation

Open PageRank 6.41 / 10
Tranco 557 Global
Source: top-1m.csv

Review summary — docker.com

Overall 85 (Mostly safe)

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

Strengths

  • Valid SSL/TLS certificate
  • SPF configured
  • DMARC configured
  • Domain age ≥ 1 year

Weaknesses

  • HSTS not set
  • CSP not set

Detailed review — docker.com

Domain review

Domain created: 1995-01-25T05:00:00Z (≈ 30y 11m). Registrar: Gandi SAS. Hosting / AS: FASTLY, US — United States. Popularity: Tranco #557, OPR 6.41/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC quarantine. Certificate valid until: 2026-01-01T12:43:09+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 301 Redirect · Server FASTLY, US. HSTS Off (preload: Unknown). Applies 0/6 security headers. DNSSEC Off. Email security: SPF On, DMARC quarantine. MTA‑STS policy: None. TLS‑RPT Off. security.txt: available (https://docker.com/.well-known/security.txt). JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

Age: about (≈ 30y 11m) (created on 1995-01-25T05:00:00Z).

GSB clean

WebRisk clean

Certificate valid until: 2026-01-01T12:43:09+00:00.

Email security: SPF On, DMARC quarantine.

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.

Missing key security headers leaves the site vulnerable to clickjacking, MIME sniffing, and data leakage.

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.

Estimated domain age
30y 11m
Registrar
Gandi SAS
SSL valid
Yes
SSL expires
2026-01-01T12:43:09+00:00
HTTP status
301
Server / ASN
FASTLY, US
Final URL
https://docker.com/
SPF
Yes
DMARC
Yes
CT wildcard usage
No
HSTS preload
Unknown
security.txt
Yes
TLS‑RPT receivers
Absent
Domain creation date
1995-01-25T05:00:00Z
Hosting / AS
FASTLY
Hosting country
United States
GSB status
No match
WebRisk status
No match
DMARC policy
quarantine
DNSSEC
Absent
Legal/contact pages
No
Structured data: Organization
Absent
Structured data: contactPoint
Absent
Registry risk (0–100)
5
dmarc_p
quarantine
dmarc_rua
mailto:q1xwnepx@ag.dmarcian.com
dmarc_ruf
mailto:q1xwnepx@fr.dmarcian.com
mixed_http
0
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-20 12:32:28
Email

Traffic signals

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

Performance

Field LCP-ms
Field INP-ms
Field CLS-
Lab LCP-ms
Lab TBT-ms
Mobile score-
Mobile measurement error: request_failed
Lab LCP-ms
Lab TBT-ms
Desktop score-
Desktop measurement error: request_failed
https://docker.com/

Security headers

  • HSTS
  • Content‑Security‑Policy
  • X‑Content‑Type‑Options
  • X‑Frame‑Options
  • Referrer‑Policy
  • Permissions‑Policy
Enable HSTS
add_header Strict-Transport-Security "max-age=15552000; includeSubDomains; preload" always;
Set CSP
This is a minimal CSP example. Adjust allowed sources to your project.
add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";
Prevent content type sniffing
add_header X-Content-Type-Options "nosniff" always;
Prevent clickjacking
add_header X-Frame-Options "SAMEORIGIN" always;
Set Referrer‑Policy
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
Set Permissions‑Policy
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;

Domain lineage

  1. 1995-01-25
    Domain registered: 1995-01-25T05:00:00Z

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB -
SPF Configured
DMARC Configured
DNSSEC No
Cookie security Absent
Mixed content (http) 0
Legal pages Absent
DMARC details
DMARC policy (p): quarantine
Aggregate reports (rua): mailto:q1xwnepx@ag.dmarcian.com
Failure reports (ruf): mailto:q1xwnepx@fr.dmarcian.com
TXT: v=DMARC1; p=quarantine; pct=100; rua=mailto:q1xwnepx@ag.dmarcian.com; ruf=mailto:q1xwnepx@fr.dmarcian.com;v=DMARC1; p=quarantine; pct=100; rua=mailto:q1xwnepx@ag.dmarcian.com; ruf=mailto:q1xwnepx@fr.dmarcian.com;
HTTP status301
Server FASTLY, US
CDN / Hosting Fastly CDN
HSTSNo
Valid until2026-01-01T12:43:09+00:00
IssuerLet's Encrypt / R13
Registrant / organizationFASTLY, US
RegistrarGandi SAS
ASN54113
Network23.185.0.0/24
Title-
Final URL: https://docker.com/

Threat insight

Mostly safe (risk 7/100)
  • Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
  • Missing key security headers leaves the site vulnerable to clickjacking, MIME sniffing, and data leakage.
  • Suspicious JavaScript patterns detected

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 20/100)
  • Suspicious JavaScript obfuscation patterns have been observed.

If unexpected popups, wallet connection requests, or download prompts appear, cancel once and re‑check via official announcements or community channels.

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 5
Suspicious JS patterns 1
Collection time: 2025-11-20T12:32:28+00:00
docker.com cdn.cookielaw.org assets.adobedtm.com googletagmanager.com google.com
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 ba431bf779787934b9493c5fb3e90b902b340b6fb0084f7d57db201c97dda210

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