Is cpi.ad.jp a scam site? Scam, spam & reviews

Score
76
HTTP status
301
https://cpi.ad.jp/
SSL/TLS
Valid
2026-04-14T23:59:59+00:00
Server/AS
CPI-NET KDDI Web Communications Inc., JP
110.50.222.18
Open site

Scores & key points

Security
Reputation
Scam risk

Caution signals

No clear warnings detected.

Reputation

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

Review summary — cpi.ad.jp

Overall 76 (Use with caution)

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

Strengths

  • Valid SSL/TLS certificate
  • SPF configured
  • DMARC configured

Weaknesses

  • HSTS not set
  • CSP not set

Detailed review — cpi.ad.jp

Domain review

Hosting / AS: CPI-NET KDDI Web Communications Inc., JP — Japan. Popularity: OPR 2.31/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC None. Certificate valid until: 2026-04-14T23: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 301 Redirect · Server CPI-NET KDDI Web Communications Inc., JP. HSTS Off (preload: Unknown). Applies 0/6 security headers. DNSSEC Off. Email security: SPF On, DMARC None. 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-04-14T23:59:59+00:00.

Email security: SPF On, DMARC none.

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-04-14T23:59:59+00:00
HTTP status
301
Server / ASN
CPI-NET KDDI Web Communications Inc., JP
Final URL
https://cpi.ad.jp/
SPF
Yes
DMARC
Yes
CT wildcard usage
Yes
HSTS preload
Unknown
security.txt
No
TLS‑RPT receivers
Absent
Hosting / AS
KDDI Web Communications Inc.
Hosting country
Japan
GSB status
No match
WebRisk status
No match
DMARC policy
None
PSI desktop
63
DNSSEC
Absent
Legal/contact pages
No
Structured data: Organization
Absent
Structured data: contactPoint
Absent
Registry risk (0–100)
5
dmarc_p
None
dmarc_rua
mailto:cpirua@cpi.ad.jp,mailto:kddi-web00001-ra@dmarc25.jp
dmarc_ruf
mailto:cpiruf@cpi.ad.jp
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-30 07:03:46
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 LCP2317.7ms
Lab TBT152ms
Desktop score63
https://cpi.ad.jp/

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;

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): none
Aggregate reports (rua): mailto:cpirua@cpi.ad.jp,mailto:kddi-web00001-ra@dmarc25.jp
Failure reports (ruf): mailto:cpiruf@cpi.ad.jp
TXT: v=DMARC1; p=none; fo=1; rua=mailto:cpirua@cpi.ad.jp,mailto:kddi-web00001-ra@dmarc25.jp; ruf=mailto:cpiruf@cpi.ad.jpv=DMARC1; p=none; fo=1; rua=mailto:cpirua@cpi.ad.jp,mailto:kddi-web00001-ra@dmarc25.jp; ruf=mailto:cpiruf@cpi.ad.jp
HTTP status301
Server CPI-NET KDDI Web Communications Inc., JP
CDN / Hosting Other CDN
HSTSNo
Valid until2026-04-14T23:59:59+00:00
IssuerDigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Registrant / organizationCPI-NET KDDI Web Communications Inc., JP
Registrar-
ASN9597
Network110.50.216.0/21
Title301 Moved Permanently
Final URL: https://cpi.ad.jp/

Threat insight

Mostly safe (risk 8/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.

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 0/100)

Before entering payment or personal information, verify the site operator/contact, HTTPS enforcement (HSTS), and the presence of DMARC and TLS‑RPT.

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 4
Collection time: 2025-11-30T07:03:46+00:00
cpi.ad.jp fonts.googleapis.com fonts.gstatic.com googletagmanager.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

Japan (JP) · ASN 9597 / KDDI Web Communications Inc.

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum 4b0ad3bf89bcf049dd0002ff87227640863e227c886d4009604d718cc581064c

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