Skip to main content

Security report for nifty.com

NIFTY Corporation · Telecommunications · Japan

Partial score · DNS & email only

75/100

0–100, higher is better. How it is calculated

NIFTY Corporation operates as a major Japanese internet service provider offering a wide range of broadband, mobile SIM, security, and media services primarily targeting Japanese consumers. The company maintains a strong market position with a comprehensive portfolio including @nifty光 broadband, NifMo mobile SIM, and various security and lifestyle services. Their digital presence is built on modern web technologies such as Next.js and is hosted via Amazon CloudFront, ensuring fast content delivery and good mobile optimization. However, the website currently lacks a valid SSL certificate, which is a critical security concern that undermines user trust and data protection. Security headers are partially implemented, but the absence of DNSSEC, CAA records, and HSTS reduces domain and transport security. The site uses multiple advertising and tracking services, with moderate user tracking and basic privacy compliance. Contact information is limited to a phone number with no visible email addresses or contact forms on the main page. Overall, the website is professionally designed with good content relevance and navigation clarity but requires urgent security improvements to protect users and enhance trust.

Scanned

NIS2 and GDPR posture

NIS2 outside view
Not assessed
GDPR outside view
Not assessed

Both readouts depend on the site's pages, which could not be loaded in this scan.

Priority findings

2 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

Need hands-on remediation? Email guard@offseq.com

Keep watching nifty.com

This scan found 10 issues across 4 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
100
Security headers
55
Email security
70
DNS health
85
Network security
100
Average
82
After the cap
75

Not counted

  • GDPR outside view: did not complete in this scan.
  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention nifty.com, from OffSeq Breach.

Total records
55,456
Employees
203
Customers
5,847
Third parties
49,406
Weak passwords
24%

Latest record dated 2026-06-10 · 121 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for nifty.com.

Select it in the checkout above.

Masked preview

  • –sso.nifty.com2026-06-10
  • –sso.nifty.com2026-06-10
  • –sso.nifty.com2026-06-07
  • –sso.nifty.com2026-06-06
  • –sso.nifty.com2026-05-28

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

NIFTY Corporation is positioned as a large telecommunications and media company in Japan, offering ISP services, mobile SIM plans, security solutions, and digital content platforms. Their business model leverages a broad service ecosystem including affiliate marketing partnerships and a points-based rewards program to engage customers. The company targets general internet users and businesses in Japan, with a strong emphasis on broadband and mobile connectivity. Partnerships with major e-commerce and advertising platforms such as Rakuten, Amazon, and ValueCommerce enhance their revenue streams. The company maintains active social media channels and community platforms to foster user engagement. Growth indicators include ongoing campaigns, service expansions like 10 Gbps broadband plans, and a diversified service portfolio. Strategic observations suggest a need to strengthen security posture and privacy compliance to maintain competitive advantage and customer trust.

Security posture

The current security maturity level of the NIFTY website is moderate to low due to the absence of a valid SSL certificate and lack of modern TLS protocol support. While some security headers are implemented to mitigate common web attacks such as clickjacking and XSS, the missing DNSSEC and CAA records expose the domain to potential DNS spoofing and unauthorized certificate issuance. No explicit incident response or vulnerability disclosure policies are found, indicating limited transparency in security governance. The website does not display cookie consent mechanisms, which may impact compliance with privacy regulations. The use of multiple third-party advertising and tracking scripts increases the attack surface and privacy risks. Overall, the security posture requires significant improvements in transport security, domain protection, and privacy compliance to align with industry best practices and regulatory requirements.

Recommendations

  1. Implement and maintain a valid SSL/TLS certificate to enable HTTPS and protect user data in transit.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated protocols to enhance encryption strength.
  3. Configure and enforce HSTS with includeSubDomains and preload to prevent protocol downgrade attacks.
  4. Deploy DNSSEC and CAA records to secure DNS infrastructure and restrict certificate issuance.
  5. Introduce a comprehensive cookie consent mechanism to comply with privacy regulations and enhance user trust.
  6. Publish clear security policies, incident response procedures, and vulnerability disclosure guidelines.
  7. Limit and audit third-party tracking and advertising scripts to reduce privacy risks and improve performance.
  8. Enhance contact options by providing verified company email addresses and contact forms for support and security reporting.
  9. Regularly review and update security headers and website components to mitigate emerging threats.
  10. Promote security awareness and transparency to strengthen the overall security culture and customer confidence.
Technical notes

Notes

The website is built using Next.js, a React-based framework, indicating a modern and scalable front-end architecture. Hosting is provided via Amazon CloudFront CDN, ensuring fast content delivery and global availability. The site uses multiple CSS stylesheets and JavaScript chunks for modular loading. Performance is rated fast, with good mobile optimization and SEO practices evident from meta tags and structured data. However, the lack of a valid SSL certificate and disabled TLS protocols represent critical technical debt and security risks. The site integrates various third-party advertising and tracking technologies, including Google Analytics, Google Tag Manager, PubMatic, Rubicon Project, and GeoEdge, which may impact privacy and performance. No CMS is explicitly detected, suggesting a custom or framework-based content management approach. Opportunities exist to modernize security infrastructure, improve accessibility, and enhance privacy compliance to reduce technical risks and support business continuity.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with nifty.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review nifty.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.