Is fc2blog.net a scam site? Scam, spam & reviews

Score ⓘ

HTTP status ⓘ

404

https://error.fc2.com/blog/e/404/?c=4b2009ap?fc2blog.net%2F

SSL/TLS ⓘ

Invalid

Server/AS ⓘ

nginx

104.244.99.50

Open site

Scores & key points

Security

Reputation

Scam risk

Caution signals ⓘ

[Low] WHOIS information is masked/private.
[Medium] No valid SSL/TLS certificate found.
[Medium] An HTTP error occurred when accessing the landing page.

Reputation

Open PageRank ⓘ 1.78 / 10

Tranco ⓘ - Global

Tranco fetch error: csv_scan_disabled

Review summary — fc2blog.net

Overall 54 (Suspicious site)

Risk signals such as WHOIS privacy or missing security headers have been identified.

Strengths

Domain age ≥ 1 year

Weaknesses

No valid SSL/TLS certificate
HSTS not set
CSP not set
SPF not configured
DMARC not configured
HTTP error on landing page

Detailed review — fc2blog.net

Domain review

Domain created: 2010-05-12T23:35:33Z (≈ 15y 7m). Registrar: TUCOWS DOMAINS, INC.. Hosting / AS: nginx — United States. Popularity: OPR 1.78/10. Reputation: GSB clean WebRisk clean.

Shop / transaction review

No mixed content detected. No mixed content detected. Structured data: Organization Absent, contactPoint Absent. Hidden text ratio 0%.

Technical review

HTTP 404 Client error · Server nginx. HSTS Off (preload: Unknown). Applies 0/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

Age: about (≈ 15y 7m) (created on 2010-05-12T23:35:33Z).

GSB clean

WebRisk clean

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.

Estimated domain age ⓘ

15y 7m

Registrar ⓘ

TUCOWS DOMAINS, INC.

Registrant / organization ⓘ

Contact Privacy Inc. Customer 0123837723

SSL valid ⓘ

HTTP status ⓘ

404

Server / ASN ⓘ

nginx / FC2-INC-2, US

Final URL ⓘ

https://error.fc2.com/blog/e/404/?c=4b2009ap?fc2blog.net%2F

SPF

DMARC

CT wildcard usage ⓘ

HSTS preload ⓘ

Unknown

security.txt ⓘ

TLS‑RPT receivers ⓘ

Absent

Domain creation date ⓘ

2010-05-12T23:35:33Z

Hosting / AS ⓘ

FC2-INC-2

Hosting country ⓘ

United States

GSB status ⓘ

No match

WebRisk status ⓘ

No match

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 ⓘ

Webshop Helpdesk

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-12-11 12:05:14

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

Open PageSpeed (mobile)

Lab LCPⓘ-ms

Lab TBTⓘ-ms

Desktop scoreⓘ-

Desktop measurement error: request_failed

Open PageSpeed (desktop)

https://error.fc2.com/blog/e/404/?c=4b2009ap?fc2blog.net%2F

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;

Configure SPF

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

Configure DMARC

v=DMARC1; p=quarantine; rua=mailto:dmarc@fc2blog.net; ruf=mailto:dmarc@fc2blog.net; fo=1

Add MX records

@  3600  MX  10  mail.fc2blog.net.

Domain lineage

2010-05-12

Domain registered: 2010-05-12T23:35:33Z

Essentials

Google Safe Browsingⓘ No match

Google Web Riskⓘ No match

AbuseIPDBⓘ 0%

SPFⓘ -

DMARCⓘ -

DNSSECⓘ No

Cookie security ⓘ Absent

Mixed content (http)ⓘ 0

Legal pages ⓘ Absent

HTTP statusⓘ404

Server ⓘ nginx

CDN / Hosting ⓘ Other CDN

HSTSⓘNo

Valid untilⓘ-

Issuerⓘ-

Registrant / organizationⓘContact Privacy Inc. Customer 0123837723

RegistrarⓘTUCOWS DOMAINS, INC.

ASNⓘ63210

Networkⓘ199.48.210.0/23

Titleⓘ404 Error - FC2ブログ

Final URL: https://error.fc2.com/blog/e/404/?c=4b2009ap?fc2blog.net%2F

Threat insight

Caution (risk 67/100)

Using invalid or expired SSL/TLS certificates triggers browser warnings and increases the risk of man‑in‑the‑middle attacks or confusion with phishing sites. Check certificate status regularly.
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 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.
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. Several risk signals are present. Before making payments or downloading files, check HTTPS enforcement (HSTS), DMARC policy, and the presence of mixed content, and compare the site in a new tab with official accounts or in‑app links. 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)

Dangerous (deep 70/100)

Unencrypted (HTTP) resources are being loaded.
Suspicious JavaScript obfuscation patterns have been observed.
Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.

If possible, configure the site to use HTTPS only and replace HTTP resources in the page with HTTPS. If unexpected popups, wallet connection requests, or download prompts appear, cancel once and re‑check via official announcements or community channels.

HTTP status (deep) 404

Set‑Cookie (count) 2

Cookie security insufficient Secure×2 / HttpOnly×2 / SameSite×2

HTTP resources (deep) 7

Top third‑party hosts 1

Suspicious JS patterns 1

Collection time: 2025-12-11T12:05:14+00:00

product.adingo.jp.eimg.jp

Show examples of HTTP resources

http://product.adingo.jp.eimg.jp/c/hybridplus/keyword.php?apikey=0158600014</code><br><code>http://product.adingo.jp.eimg.jp/c/hybridplus/keyword.php?apikey=0158600002</code><br><code>http://product.adingo.jp.eimg.jp/c/hybridplus/keyword.php?apikey=0158600003</code><br><code>http://product.adingo.jp.eimg.jp/c/hybridplus/keyword.php?apikey=0158600007</code><br><code>http://product.adingo.jp.eimg.jp/c/hybridplus/keyword.php?apikey=0158600010</code><br><code>http://product.adingo.jp.eimg.jp/c/hybridplus/keyword.php?apikey=0158600012</code><br><code>http://product.adingo.jp.eimg.jp/c/hybridplus/keyword.php?apikey=0158600004

Iframe hosts

media5.fc2.com

Set‑Cookie (samples)

bloguid=9abad897-0ec5-418c-8823-17f5d4a7b156; expires=Fri, 11-Dec-2026 12:05:14 GMT; Max-Age=31536000</code><br><code>cookietest=test; expires=Sun, 21-Dec-2025 12:05:13 GMT; Max-Age=863999; path=/

User scenarios

If you make a payment on this site

Entering card, bank or wallet details on this site is high risk. Only proceed after confirming the official domain via trusted channels. Mixed or non-encrypted (HTTP) resources or weak TLS can expose payment data or session tokens on some networks. Missing or weak DMARC lets attackers send spoofed payment emails. Type the domain manually instead of clicking links in unexpected messages.

If you log in or enter personal data

Entering passwords or sensitive identifiers on this site is high risk. Account takeover or identity abuse is more likely; verify the official domain or app first. 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.