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

Score
74
HTTP status
301
https://nicovideo.jp/
SSL/TLS
Valid
2026-12-13T23:59:59+00:00
Server/AS
AMAZON-02, US
54.230.62.106
Open site

Scores & key points

Security
Reputation
Scam risk

Overview

Label
ニコニコ動画

日本の動画共有サービス

Caution signals

No clear warnings detected.

Reputation

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

Review summary — nicovideo.jp

Overall 74 (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 — nicovideo.jp

Domain review

Hosting / AS: AMAZON-02, US — United States. Popularity: Tranco #3444, OPR 5.89/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC None. Certificate valid until: 2026-12-13T23: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 AMAZON-02, US. 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-12-13T23: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-12-13T23:59:59+00:00
HTTP status
301
Server / ASN
AMAZON-02, US
Final URL
https://nicovideo.jp/
SPF
Yes
DMARC
Yes
CT wildcard usage
No
HSTS preload
Unknown
security.txt
No
TLS‑RPT receivers
Absent
Hosting / AS
AMAZON-02
Hosting country
United States
GSB status
No match
WebRisk status
No match
DMARC policy
None
PSI mobile
79
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:report@dmarcreports.nicovideo.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
Corona Virus - High Risk

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-22 18:24:03
Email

Traffic signals

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

Performance

Field LCP3011ms
Field INP-ms
Field CLS0.15
Lab LCP3944.6ms
Lab TBT78ms
Mobile score79
Lab LCP-ms
Lab TBT-ms
Desktop score-
Desktop measurement error: request_failed
https://nicovideo.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;
Add MX records
@  3600  MX  10  mail.nicovideo.jp.

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB -
SPF Configured
DMARC none
DNSSEC No
Cookie security Absent
Mixed content (http) 0
Legal pages Absent
DMARC details
DMARC policy (p): none
Aggregate reports (rua): mailto:report@dmarcreports.nicovideo.jp
TXT: v=DMARC1;p=none;pct=100;rua=mailto:report@dmarcreports.nicovideo.jpv=DMARC1;p=none;pct=100;rua=mailto:report@dmarcreports.nicovideo.jp
HTTP status301
Server AMAZON-02, US
CDN / Hosting AWS CloudFront
HSTSNo
Valid until2026-12-13T23:59:59+00:00
IssuerAmazon / Amazon RSA 2048 M01
Registrant / organizationAMAZON-02, US
Registrar-
ASN16509
Network54.230.0.0/15
Title301 Moved Permanently
Final URL: https://nicovideo.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 10/100)
  • Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.

For session/login cookies, always set Secure, HttpOnly, and SameSite.

HTTP status (deep) 200
Set‑Cookie (count) 1
Cookie security insufficient Secure×1 / HttpOnly×1 / SameSite×1
HTTP resources (deep) 0
Top third‑party hosts 6
Collection time: 2025-11-22T18:24:03+00:00
resource.video.nimg.jp sp.nicovideo.jp nicovideo.jp googletagmanager.com res.ads.nicovideo.jp assets.embed.res.nimg.jp
Iframe hosts
googletagmanager.com
Set‑Cookie (samples)
nicosid=1763835843.23500388; expires=Tue, 20 Nov 2035 18:24:03 GMT; Max-Age=315360000; path=/; domain=.nicovideo.jp

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. 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

United States (US) · ASN 16509 / AMAZON-02

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum 41d9976c7c84b1f017363fc4e61b88f49129fd8f17aaee8f6c166681283de5bf

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