Is mysql.com a scam site? Scam, spam & reviews
Scores & key points
Overview
SQLデータベースエンジン
+62 Show more languages
Caution signals ⓘ
- [Low] Security headers such as HSTS and CSP are missing or insufficient.
- [Low] Without SPF/DMARC, email sender spoofing risk is increased.
- [Low] Cookie security attributes are insufficient (total 2).
Reputation
Review summary — mysql.com
Overall 90 (Mostly safe)Multiple security indicators are favorable and there are few major risk signals.
Strengths
- Valid SSL/TLS certificate
- HSTS enabled
- DMARC configured
- Domain age ≥ 1 year
Weaknesses
- CSP not set
- SPF not configured
Detailed review — mysql.com
Domain review
Domain created: 1999-02-03T05:00:00Z (≈ 26y 10m). Registrar: MarkMonitor Inc.. Hosting / AS: ORACLE-BMC-31898, US — United States. Popularity: Tranco #491, OPR 6.46/10. Reputation: GSB clean WebRisk clean. Email security: SPF Off, DMARC None. Certificate valid until: 2026-03-04T23:59:59+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 ORACLE-BMC-31898, US. HSTS Off (preload: Unknown). Applies 3/6 security headers. DNSSEC Off. Email security: SPF Off, DMARC None. MTA‑STS policy: None. TLS‑RPT Off. security.txt: not available. Missing cookie attributes: Secure×1 / HttpOnly×0 / SameSite×1. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
Age: about (≈ 26y 10m) (created on 1999-02-03T05:00:00Z).
GSB clean
WebRisk clean
Certificate valid until: 2026-03-04T23:59:59+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.
Cookies without Secure / HttpOnly / SameSite can be vulnerable to theft or session fixation attacks.
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 13:55:56
Claim website ownership
Traffic signals
Performance
Security headers
- HSTS ⓘ
- Content‑Security‑Policy ⓘ
- X‑Content‑Type‑Options ⓘ
- X‑Frame‑Options ⓘ
- Referrer‑Policy ⓘ
- Permissions‑Policy ⓘ
add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
v=spf1 include:_spf.google.com ~all
Set-Cookie: name=value; Path=/; Secure; HttpOnly; SameSite=Lax
MySQL_S=u9ftm9a31hg94epg9kordda5ms7ql828
Domain lineage
-
1999-02-03Domain registered: 1999-02-03T05:00:00Z
Essentials
DMARC details
v=DMARC1; p=none; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com; fo=1v=DMARC1; p=none; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com; fo=1Threat insight
- 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.
- HTTP resources found on HTTPS page
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)
- The site is blocking automated access, limiting detailed inspection.
- Unencrypted (HTTP) resources are being loaded.
- Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.
Confirm that you accessed this site via an official link or in‑app navigation, and before payment or login, verify that the domain in the address bar matches the official one. If possible, configure the site to use HTTPS only and replace HTTP resources in the page with HTTPS.
Show examples of HTTP resources
http://www.oracleimg.com/us/assets/metrics/ora_ocom.js
Set‑Cookie (samples)
AK_NETWORKTYPE=ESSL; expires=Thu, 20-Nov-2025 13:57:56 GMT
User scenarios
If you make a payment on this site
Some technical or reputation signals suggest caution. Check the address bar, HTTPS and browser warnings before entering payment details. Mixed or non-encrypted (HTTP) resources or weak TLS can expose payment data or session tokens on some networks.
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 ⓘ
History
Change ⓘ --Recently added sites
Reviews
Average - / total 0
Checksum 382b4da63b963b24e0c24fed1a9acf9cff888dc9469d0b4a69c0465b3794757e
Social ⓘ
Platforms that this site may be using.