Skip to main content

Security report for taskon.com

Technology · N/a

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

Security score

61/100

Risk levelMedium

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

Ticklish Techs is a niche technical blog primarily focused on .NET programming and DIY electronics projects, including home automation. The website provides detailed technical articles, code snippets, and project documentation aimed at developers and technology enthusiasts. The blog has a consistent posting history dating back to 2008, indicating a stable content presence. Technically, the site is built on WordPress 5.7.11 and uses standard web technologies such as JavaScript and CSS. While the site is functional and content-rich, it lacks modern security enhancements such as DNSSEC and security headers, and it does not provide privacy or cookie policies, which are important for compliance with regulations like GDPR. The site uses minimal tracking via WordPress stats and does not display advertising or affiliate marketing. Overall, the website is trustworthy and safe for general audiences but could improve its security posture and privacy compliance.

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 taskon.com

This scan found 26 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. 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
62
Security headers
15
Email security
70
DNS health
70
Network security
100
GDPR outside view
50
Average
61

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

No leaked records found

Breach holds no records for taskon.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

The website operates as a small-scale content blog without explicit commercial activities or business entity disclosures. Its market positioning is that of a specialized technical resource for .NET developers and DIY electronics hobbyists. The business model appears to be knowledge sharing and community engagement rather than direct monetization. The target audience includes developers interested in .NET, home automation, and electronics projects. The blog maintains a consistent publishing schedule and provides detailed technical content, which supports its credibility. There is no evidence of partnerships, subsidiaries, or parent companies. The site links to related technical resources and GitHub repositories, indicating an ecosystem of open-source and community-driven projects.

Security posture

The website employs HTTPS and has domain registration protections such as clientTransferProhibited and clientUpdateProhibited statuses, which help prevent unauthorized domain changes. However, the absence of DNSSEC and security headers like Content-Security-Policy and HSTS reduces its defense-in-depth. No explicit security or incident response policies are published, and no vulnerability disclosure or security.txt files are found. The WordPress version used is outdated, which could expose the site to known vulnerabilities if not patched. Minimal tracking is present, but privacy policies are missing, which is a compliance risk. Overall, the security posture is moderate but could be significantly improved by updating software, enabling DNSSEC, adding security headers, and publishing privacy and security policies.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement security headers such as Content-Security-Policy, X-Frame-Options, and HSTS to protect against common web attacks.
  3. Update WordPress to the latest version to mitigate vulnerabilities and improve performance.
  4. Publish comprehensive privacy and cookie policies to comply with GDPR and other privacy regulations.
  5. Add explicit contact information including company emails and phone numbers to improve business credibility and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A mostly .NET but also some other cool techs blog featuring technical articles, DIY projects, and programming insights.
Key services
Technical blog articles, DIY electronics project documentation, Programming tutorials and insights
Content quality
good
Branding
moderate

Technology

Stack
WordPress 5.7.11, PHP, JavaScript, CSS
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Use of HTTPS (implied by URLs)
  • ClientTransferProhibited and clientUpdateProhibited domain status

Analytics and tracking

Services
WordPress Stats (stats.wordpress.com)
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
stats.wordpress.com
Transparency
basic

Site quality

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

Key observations

  1. Website is a technical blog focused on .NET and DIY electronics projects.
  2. Content is accessible and well-structured with dated posts and author information.
  3. No privacy, cookie, or terms of service policies found.
  4. No explicit contact emails or phone numbers found; contact form available.
  5. No security or incident response policies published.
  6. No vulnerability disclosure or security.txt found.
  7. Uses WordPress CMS version 5.7.11, which is somewhat outdated (latest versions are higher).
  8. No advanced security headers detected in HTML content.
  9. External links mostly to technical resources and related projects.
  10. Minimal tracking via WordPress stats pixel.
Technical notes

Notes

The website is built on WordPress 5.7.11, which is an older version and may lack recent security patches and features. The site uses standard web technologies including JavaScript and CSS, with some inline scripts for emoji support and WordPress stats tracking. Performance is moderate with no advanced optimization detected. Mobile optimization and accessibility are basic but functional. SEO optimization is minimal with basic meta tags and RSS feeds. The hosting provider is not explicitly identified, but the domain registrar is Tucows Domains Inc. The site lacks modern security features such as DNSSEC and security headers, which are recommended for improved security posture. Overall, the technical infrastructure is stable but could benefit from modernization and enhanced security configurations.
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 taskon.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 taskon.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.