Skip to main content

Security report for kdfashioncompany.com

X (formerly Twitter) · Technology · N/a

Low risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

78/100

Risk levelLow

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

The analyzed website page is part of the X.com domain, formerly known as Twitter, a major global social media platform. The page content is user-generated promotional material targeting fashion brands and style influencers, indicating the platform's use for marketing and advertising. The business operates at an enterprise scale within the technology industry, providing social networking and content sharing services. The domain is well-established, created in 1993, and registered with a reputable registrar, GoDaddy.com, LLC, reflecting high legitimacy and trustworthiness. From a technical perspective, the website employs modern web technologies including JavaScript and web fonts, with moderate performance and good mobile optimization. However, explicit frameworks or CMS platforms are not clearly identified. The website lacks visible security headers and formal privacy or cookie policies on the analyzed page, indicating gaps in privacy compliance and security best practices. No contact information or incident response channels are disclosed, limiting transparency and user trust. Security posture is weak based on the provided HTML content, with no detected security headers or explicit security policies. The domain's WHOIS data is consistent and trustworthy, with no privacy protection or suspicious patterns. No WAF or blocking mechanisms are detected, allowing full content access. Overall, the website demonstrates moderate business credibility but requires improvements in privacy compliance, security policies, and transparency to enhance user trust and regulatory adherence. Strategic recommendations include publishing comprehensive privacy and cookie policies, implementing security headers, enabling DNSSEC, and providing clear contact information for security incidents and data protection officers. These steps will improve the platform's security posture, privacy compliance, and overall trustworthiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
73/ 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

3 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching kdfashioncompany.com

This scan found 18 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
52
Security headers
80
Email security
80
DNS health
85
Network security
100
GDPR outside view
73
Average
78

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

X.com operates as a leading social media platform with a broad user base and diverse content, including promotional posts for fashion brands. Its business model centers on advertising and content sharing, targeting general social media users and niche audiences such as style influencers. The platform's market position is strong, supported by a long domain history and consistent branding. Revenue streams likely include advertising and sponsored content. The platform's partnership ecosystem includes various external domains for content delivery and APIs, though no direct partner or subsidiary domains were identified in the analyzed content. Growth indicators include active user engagement and content diversity. Strategic observations highlight the need for enhanced privacy and security transparency to maintain competitive advantage and regulatory compliance.

Security posture

The current security maturity level of the website is low based on the analyzed HTML content. Key vulnerabilities include absence of security headers, lack of privacy and cookie policies, and no visible incident response or security contact information. Compliance gaps with GDPR and other privacy regulations are evident due to missing policy disclosures. Data protection practices are not explicitly stated, and incident response readiness cannot be assessed. The security culture appears limited on the public-facing page. Business impact of these gaps includes potential regulatory risks and reduced user trust. Recommendations focus on implementing security best practices, publishing comprehensive policies, and establishing clear incident response channels to improve security posture and compliance.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy with clear GDPR compliance statements.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Enable DNSSEC for the domain to enhance DNS security.
  4. Provide clear contact information for security incidents, including dedicated security and abuse email addresses.
  5. Conduct regular security audits and vulnerability assessments to identify and remediate potential risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
X (formerly Twitter)
Description
Social media platform hosting user-generated content including promotional posts such as fashion brand marketing.
Key services
Microblogging, Social networking, Content sharing, Advertising platform
Content quality
basic
Branding
consistent

Technology

Stack
JavaScript, woff2 fonts, TailwindCSS
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a social media platform page with user-generated promotional content.
  2. No privacy, cookie, or terms of service policies found on the analyzed page.
  3. No contact information or security policies disclosed on the page.
  4. No security headers or explicit security best practices detected in the HTML content.
  5. Domain WHOIS data indicates a long-established, legitimate domain with no privacy protection.
  6. No WAF or blocking mechanisms detected; content is fully accessible.
  7. Technical stack uses modern web fonts and JavaScript but lacks explicit framework indicators.
  8. Advertising and analytics tools are not explicitly detected in the provided HTML content.
Technical notes

Notes

The website uses modern web fonts (TwitterChirp) and JavaScript resources loaded from trusted domains. The domain is registered with GoDaddy.com, LLC, indicating reliable hosting and domain management. Performance is moderate with good mobile optimization, but accessibility and SEO optimizations are basic. No CMS or specific frameworks are detected in the provided HTML. The technical infrastructure supports a large-scale social media platform but lacks visible advanced security configurations. Opportunities exist to modernize security implementations and improve privacy compliance. Technical risks include potential exposure to security threats due to missing headers and policies.
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 kdfashioncompany.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 kdfashioncompany.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.