Is google.com a scam site? Scam, spam & reviews
Scores & key points
Overview
アメリカの多国籍テクノロジー企業
+178 Show more languages
Caution signals ⓘ
No clear warnings detected.
Reputation
Review summary — google.com
Overall 86 (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 — google.com
Domain review
Domain created: 1997-09-15T04:00:00Z (≈ 28y 2m). Registrar: MarkMonitor Inc.. Hosting / AS: GOOGLE, US — United States. Popularity: Tranco #1, OPR 10.00/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC reject. Certificate valid until: 2026-01-19T08:33:50+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 GOOGLE, US. HSTS Off (preload: Unknown). Applies 1/6 security headers. DNSSEC Off. Email security: SPF On, DMARC reject. MTA‑STS policy: Enforced. TLS‑RPT On (sts-reports@google.com). security.txt: available (https://google.com/.well-known/security.txt). JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
Age: about (≈ 28y 2m) (created on 1997-09-15T04:00:00Z).
GSB clean
WebRisk clean
Certificate valid until: 2026-01-19T08:33:50+00:00.
Email security: SPF On, DMARC reject.
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.
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.
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-16 12:06:27
Claim website ownership
Performance
Security headers
- HSTS ⓘ
- Content‑Security‑Policy ⓘ
- X‑Content‑Type‑Options ⓘ
- X‑Frame‑Options ⓘ
- Referrer‑Policy ⓘ
- Permissions‑Policy ⓘ
add_header Strict-Transport-Security "max-age=15552000; includeSubDomains; preload" always;
add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";
add_header X-Content-Type-Options "nosniff" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
Essentials
DMARC details
v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.comv=DMARC1; p=reject; rua=mailto:mailauth-reports@google.comThreat insight
- 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)
- Suspicious JavaScript obfuscation patterns have been observed.
- Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.
If unexpected popups, wallet connection requests, or download prompts appear, cancel once and re‑check via official announcements or community channels. For session/login cookies, always set Secure, HttpOnly, and SameSite.
Set‑Cookie (samples)
AEC=AaJma5scqGFqUdoVSeJKFMFh-hW3ySmnk1uXtqXveXgxIxsN7gwsPm2I3Q; expires=Fri, 15-May-2026 12:06:27 GMT; path=/; domain=.google.com; Secure; HttpOnly; SameSite=lax</code><br><code>NID=526=MqRByueDR5Cwb7HpNN4ZHjAJR-s4_a-6P7uR_U1yS1BvGkwIGeLoOCoA3SkhSo3mmRc_vcb8eXfvPfkreY0YDOPL17N5xaAVoGfhK5JKITMh2_9XjkpymTqSHx1wVpvdlJnkcV-cKWx93PxLhCfSave4gy0z9lthejFBDabDC6ugZOuxUPQNxFH1lcnxcNDAweRKK_gogBYBlpiSqA; expires=Mon, 18-May-2026 12:06:27 GMT; path=/; domain=.google.com; HttpOnly
Server location ⓘ
History
Change ⓘ --Recently added sites
Reviews
Average - / total 0
Checksum 5ea3e5835c42c598c29bbc7a4988860b6a625a9a5f661db77dd5acd47841ba2e
Analyzing
Collecting various signals and public data.
- Start
- Fetch DNS / WHOIS
- Check HTTP response
- Verify SSL/TLS
- Query reputation
- Collect PageSpeed data
- Analyze security headers
- Check email security
- Integrate extended signals
- Build report