Skip to main content

Security report for p73.org

Other · Japan

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

63/100

Risk levelMedium

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

The website www.p73.org is a Japanese-language content site focused on skincare advice and product recommendations for women in their 50s. It provides educational articles about skin changes with age, proper cleansing techniques, and ranks popular facial cleansing products with affiliate links. The site targets mature female consumers interested in maintaining healthy skin and uses affiliate marketing as its primary business model. Technically, the site is built with basic HTML, CSS, and JavaScript, with moderate mobile optimization and basic SEO features. Security posture is limited, with no evident security headers or privacy policies, and WHOIS data is unavailable, which impacts trustworthiness. Analytics are implemented via Research Artisan Pro tracking scripts. Overall, the site is functional but lacks advanced security and privacy compliance features.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

7 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

Keep watching p73.org

This scan found 25 issues across 6 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. The full timeline opens with your unlock code.

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
72
Security headers
15
Email security
70
DNS health
70
Network security
100
GDPR outside view
50
Average
63

Not counted

  • 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

Technical appendix

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

Business context

Business profile

The site occupies a niche market segment targeting Japanese women aged 50 and above seeking skincare guidance. Its competitive advantage lies in specialized content tailored to this demographic and affiliate marketing partnerships with skincare brands. Revenue is likely generated through affiliate commissions. The site links extensively to external affiliate networks and related topical sites, indicating a broad partnership ecosystem. However, the absence of clear business contact information and registrant data limits transparency. Growth potential depends on improving trust signals and expanding content depth.

Security posture

The website currently exhibits a low to moderate security maturity level. It lacks critical security headers and privacy compliance documentation such as privacy and cookie policies. No incident response or security contact information is provided. The absence of WHOIS registrant data raises concerns about domain legitimacy and accountability. While no direct vulnerabilities were detected in the content, the site would benefit from implementing HTTPS (if not already), security headers, and transparent privacy practices to enhance user trust and regulatory compliance.

Recommendations

  1. Implement and enforce HTTPS with a strong SSL/TLS configuration to secure user connections.
  2. Add comprehensive privacy and cookie policies to comply with GDPR and other privacy regulations.
  3. Publish clear contact information including business email and phone number to improve transparency.
  4. Configure security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Obtain and publish WHOIS registrant information or use a verified domain registration to improve legitimacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The website provides detailed information and product recommendations focused on facial cleansing and skincare for women in their 50s. It includes educational content about skin changes in the 50s, proper cleansing techniques, ingredient advice, and ranked product promotions.
Key services
Skincare advice, Product rankings, Affiliate product referrals
Content quality
good
Branding
moderate

Technology

Stack
HTML5, CSS, JavaScript
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
40/100

Analytics and tracking

Services
Research Artisan Pro
Tracking level
moderate
Privacy practices
poor

Advertising

Ad networks
A8.net, Afi-b.com
Tracking pixels
Research Artisan Pro
Transparency
basic

Site quality

Design
basic
User experience
basic
Content relevance
good
Navigation
basic
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website content is fully accessible and not blocked by WAF or security mechanisms.
  2. Content is focused on skincare for women in their 50s with product recommendations and educational articles.
  3. No privacy policy, cookie policy, or terms of service pages detected.
  4. No contact emails, phone numbers, or social media links found on the site.
  5. WHOIS data is unavailable or malformed, limiting domain trust verification.
  6. Site uses affiliate marketing with multiple external affiliate links.
  7. Tracking scripts from Research Artisan Pro are present for analytics.
  8. No security headers or advanced security configurations detected in provided data.
  9. Site uses Shift_JIS charset and Japanese language content.
  10. Mobile optimization and accessibility are basic but functional.
Technical notes

Notes

The website uses a simple technology stack with static HTML, CSS, and JavaScript. It includes affiliate marketing scripts and tracking pixels from Research Artisan Pro. The site uses the Shift_JIS charset and is primarily in Japanese. Mobile optimization is basic but present. SEO is minimally addressed with meta viewport and canonical tags. No CMS or advanced frameworks were detected. Performance appears moderate but could be improved with modern optimization techniques. Accessibility features are minimal. The site would benefit from modernization including responsive design improvements, accessibility enhancements, and stronger technical SEO.
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 p73.org. 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 p73.org.

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.