Skip to main content

Security report for nectoday.com

Other · N/a

Partial score · DNS & email only

50/100

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

The website nectoday.com is currently inaccessible due to a JavaScript-based proof-of-work CAPTCHA challenge page designed to verify client connection security before granting access. This security mechanism effectively blocks automated access and prevents direct content retrieval, resulting in minimal visible content limited to a robot challenge screen. The domain is registered with GoDaddy.com, LLC since 2008, indicating a mature domain age and stable registration status. However, no business, contact, or policy information is exposed on this page, limiting the ability to assess the company's market position or services. The technical infrastructure includes custom JavaScript for CAPTCHA proof-of-work and uses AWS Cloudfront CDN for content delivery. Security best practices such as DNSSEC and security headers are not evident. Overall, the site’s security posture is moderate due to the challenge mechanism but lacks transparency and compliance documentation.

Scanned

3 of 7 checks could not complete. The site may be unreachable or blocking automated scans, so the results below cover only what could be checked. Try a rescan later.

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
4of 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

6 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 nectoday.com

This scan found 13 issues across 3 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

Security headers
20
DNS health
80
GDPR outside view
50
Average
50

Not counted

  • SSL/TLS: did not complete in this scan.
  • Email security: did not complete in this scan.
  • Network security: 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

Technical appendix

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

Business context

Business profile

Due to the blocking security challenge, no direct business information, contact details, or service descriptions are available. The domain age suggests an established presence, but the lack of exposed content or metadata prevents analysis of market positioning, business model, or partnerships. No social media or external business links are found. The site appears to be protecting itself from automated access or abuse, which may indicate a business with sensitive or high-value content behind the challenge.

Security posture

The site employs a custom JavaScript proof-of-work CAPTCHA challenge to mitigate automated access, which is a strong security control against bots. However, the absence of DNSSEC, security headers, and visible security policies reduces overall security maturity. No vulnerabilities or exposed sensitive data are detected on the challenge page. Incident response and vulnerability disclosure information are not provided. The security score is moderate but limited by lack of transparency and standard security headers.

Recommendations

  1. Implement DNSSEC to enhance DNS security and prevent spoofing.
  2. Add standard security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options.
  3. Publish clear privacy, cookie, and terms of service policies accessible without challenge.
  4. Provide visible contact information and incident response channels for security issues.
  5. Improve accessibility and SEO metadata to enhance user experience and discoverability.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Page is a JavaScript-based proof-of-work CAPTCHA challenge blocking direct access to content, indicating a WAF or security challenge. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Description
Checking the site connection security
Content quality
poor
Branding
moderate

Technology

Stack
JavaScript, Web Workers, SHA1 hashing, Blob URLs
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100
Good practices seen
  • Use of a JavaScript-based proof-of-work CAPTCHA challenge

Analytics and tracking

Tracking level
minimal
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 blocked by a JavaScript-based proof-of-work CAPTCHA challenge
  2. No visible business or contact information on the page
  3. No privacy, cookie, or terms of service policies found
  4. No forms or data collection fields present
  5. No social media or external business links detected except CDN domain
  6. WHOIS data shows a long-registered domain with standard registrar protections
  7. Page is minimal and designed to verify client connection security before access
Technical notes

Notes

The website uses advanced JavaScript including Web Workers and cryptographic hashing (SHA1) to implement a proof-of-work CAPTCHA challenge. Content is served via AWS Cloudfront CDN. The page is minimal with no forms or interactive elements beyond the challenge script. No CMS or frameworks are detected. Performance is moderate given the challenge complexity. Mobile optimization and accessibility are basic. SEO metadata is minimal and robots meta tag disallows indexing. The technical setup prioritizes security over content accessibility.
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 nectoday.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 nectoday.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.