Is web.dev a scam site? Scam, spam & reviews

Score ⓘ

HTTP status ⓘ

200

https://web.dev/

SSL/TLS ⓘ

Valid

2026-01-19T08:33:43+00:00

Server/AS ⓘ

GOOGLE, US

2001:4860:4802:32::1b

Open site

Scores & key points

Security

Reputation

Scam risk

Caution signals ⓘ

No clear warnings detected.

Reputation

Open PageRank ⓘ 6.85 / 10

Tranco ⓘ 2604 Global

Source: top-1m.csv

Review summary — web.dev

Overall 78 (Use with caution)

Some security settings are missing or not disclosed, so it should be used with care.

Strengths

Valid SSL/TLS certificate
HSTS enabled
CSP enabled

Weaknesses

SPF not configured
DMARC not configured

Detailed review — web.dev

Domain review

Hosting / AS: GOOGLE, US — United States. Popularity: Tranco #2604, OPR 6.85/10. Reputation: GSB clean WebRisk clean. Certificate valid until: 2026-01-19T08:33:43+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 GOOGLE, US. HSTS Off (preload: Preloaded). Applies 3/6 security headers. DNSSEC Off. MTA‑STS policy: None. TLS‑RPT Off. security.txt: not available. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

GSB clean

WebRisk clean

Certificate valid until: 2026-01-19T08:33:43+00:00.

Applies 3/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.

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.

If DMARC is absent or set to p=none, protection against sender spoofing is weak. Consider quarantine/reject policies.

Without MTA‑STS, SMTP TLS enforcement is weaker.

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

Without security.txt, the vulnerability disclosure channel is unclear and response may be delayed.

SSL valid ⓘ

Yes

SSL expires ⓘ

2026-01-19T08:33:43+00:00

HTTP status ⓘ

200

Server / ASN ⓘ

GOOGLE, US

Final URL ⓘ

https://web.dev/

SPF

DMARC

CT wildcard usage ⓘ

HSTS preload ⓘ

Preloaded

security.txt ⓘ

TLS‑RPT receivers ⓘ

Absent

Hosting / AS ⓘ

GOOGLE

Hosting country ⓘ

United States

GSB status ⓘ

No match

WebRisk status ⓘ

No match

PSI mobile ⓘ

PSI desktop ⓘ

DNSSEC ⓘ

Absent

Legal/contact pages

Structured data: Organization ⓘ

Absent

Structured data: contactPoint ⓘ

Absent

Registry risk (0–100) ⓘ

mixed_http ⓘ

JS obfuscation score ⓘ

Payment logo count ⓘ

Hidden text ratio (%) ⓘ

Cross‑domain POST form count ⓘ

External host logos/icons ⓘ

YARA matches ⓘ

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-17 11:48:18

Performance

Field LCPⓘ3096ms

Field INPⓘ-ms

Field CLSⓘ0

Lab LCPⓘ4130.7ms

Lab TBTⓘ523.5ms

Mobile scoreⓘ60

Open PageSpeed (mobile)

Lab LCPⓘ1586ms

Lab TBTⓘ516.5ms

Desktop scoreⓘ68

Open PageSpeed (desktop)

https://web.dev/

Security headers

HSTS ⓘ
Content‑Security‑Policy ⓘ
X‑Content‑Type‑Options ⓘ
X‑Frame‑Options ⓘ
Referrer‑Policy ⓘ
Permissions‑Policy ⓘ

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;

Configure SPF

v=spf1 include:_spf.google.com ~all

Configure DMARC

v=DMARC1; p=quarantine; rua=mailto:dmarc@web.dev; ruf=mailto:dmarc@web.dev; fo=1

Add MX records

@  3600  MX  10  mail.web.dev.

Essentials

Google Safe Browsingⓘ No match

Google Web Riskⓘ No match

AbuseIPDBⓘ 20%

SPFⓘ -

DMARCⓘ -

DNSSECⓘ No

Cookie security ⓘ Absent

Mixed content (http)ⓘ 0

Legal pages ⓘ Absent

HTTP statusⓘ200

ServerⓘGOOGLE, US

HSTSⓘNo

Valid untilⓘ2026-01-19T08:33:43+00:00

IssuerⓘGoogle Trust Services / WR2

Registrant / organizationⓘGOOGLE, US

Registrarⓘ-

ASNⓘ15169

Networkⓘ216.239.32.0/19

Titleⓘweb.dev

Final URL: https://web.dev/

Threat insight

Mostly safe (risk 18/100)

Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
Without SPF, resistance to email sender spoofing is low. We recommend setting SPF records on any domain that sends email.
If DMARC is absent or set to p=none, protection against sender spoofing is weak. Consider quarantine/reject policies.

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.