Skip to main content

Security report for cottonclassic.com

Other · N/a

Medium risk. 10 critical or high findings in Email security, Security headers and 3 other checks.

Security score

55/100

Risk levelMedium

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

The website cottonclassic.com appears to be inactive or parked, with minimal content consisting primarily of a hidden tracking image and an iframe embedding content from a suspicious external domain. There is no visible business information, contact details, or privacy and cookie policies, which severely limits the ability to assess the site's legitimacy or business operations. The domain is registered since 2004 but uses nameservers indicating it is for sale, suggesting it is not currently in active use for a legitimate business. Technically, the site lacks modern web standards, security headers, and SEO optimization, and the embedded iframe raises potential security concerns. Overall, the site exhibits poor content quality, weak technical implementation, and a low security posture.

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

10 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…

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

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

Keep watching cottonclassic.com

This scan found 27 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
57
Security headers
15
Email security
60
DNS health
50
Network security
100
GDPR outside view
50
Average
55

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

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 cottonclassic.com, from OffSeq Breach.

No leaked records found

Breach holds no records for cottonclassic.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

No meaningful business intelligence can be derived from the current website content. The absence of company details, contact information, or service descriptions indicates the domain is likely parked or unused. The domain age suggests it may have been used previously, but current indicators show no active business presence or market positioning. There are no signs of partnerships, certifications, or business model information.

Security posture

The security posture is weak due to the lack of HTTPS information, absence of security headers, and the presence of an iframe loading content from an untrusted external source. The domain's DNS setup with nameservers pointing to domain-for-sale services further reduces trust. No incident response or security policies are found, and no vulnerability disclosure or security.txt files are present. These factors indicate a high risk of security issues if the site were to be used actively.

Recommendations

  1. Remove or thoroughly audit the embedded iframe content to eliminate potential security risks.
  2. Enable DNSSEC and use reputable nameservers to improve domain security.
  3. Implement HTTPS with a valid SSL certificate and configure standard security headers (CSP, HSTS, X-Frame-Options).
  4. Add clear privacy and cookie policies to comply with GDPR and other regulations.
  5. Provide legitimate business information and contact details to improve trust and credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
10/100

Analytics and tracking

Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is minimal and mostly consists of a hidden 0x0 pixel image and an iframe embedding content from a suspicious external domain.
  2. No visible business information, contact details, or policies found.
  3. No metadata, Open Graph, or structured data present.
  4. No forms or user input fields detected.
  5. No social media links or emails found.
  6. No security headers or HTTPS information available from provided data.
  7. Domain WHOIS data shows domain is old but nameservers indicate domain is for sale.
  8. Potential security risk due to iframe embedding from unknown external source.
  9. No privacy or cookie policies detected; no GDPR compliance indicators.
  10. No evidence of business legitimacy or active operation.
Technical notes

Notes

The website lacks any detectable CMS or modern frameworks and does not include metadata or structured data. The HTML content is minimal and includes a hidden tracking image and an iframe from a suspicious domain. There is no evidence of performance optimization or accessibility features. The domain uses suspicious nameservers indicating it is parked or for sale, which is a technical risk. Overall, the technical implementation is poor and outdated, with significant modernization needed to support a legitimate business presence.
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 cottonclassic.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 cottonclassic.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.