Skip to main content

Security report for teamo.se

teamo · Technology · Sweden

High risk. 11 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

49/100

Risk levelHigh

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

The website teamo.se represents a small Swedish telecommunication subscription service project that has been discontinued as of 2023. The founders have shifted focus to other ventures such as Flowby and Techskaparna. The site is a simple static site built with Jekyll, hosted with AWS DNS services, and contains minimal content primarily announcing the closure of the service. There is no evidence of active data collection, forms, or advanced technical infrastructure. Security posture is basic with no DNSSEC, no security headers, and no visible HTTPS confirmation. Privacy and cookie policies are absent, indicating low compliance with GDPR standards. Contact information is limited to a personal/business email of one founder. Overall, the site serves as an informational closure notice rather than an active business platform.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 100 · Critical
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

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

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

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

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

Keep watching teamo.se

This scan found 30 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
67
Security headers
15
Email security
40
DNS health
60
Network security
100
GDPR outside view
10
Average
49

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

Teamo operated as a small subscription-based telecommunication service targeting Swedish users. The business model was likely direct-to-consumer subscriptions. The market position was niche and hobbyist, with no indication of scale or enterprise operations. The founders have diversified into other technology projects, indicating a shift away from this business. The lack of formal policies and limited contact information suggests a small-scale operation without extensive compliance or corporate infrastructure. The partnership ecosystem includes related projects by the founders, but no formal subsidiaries or parent companies are identified.

Security posture

The security maturity of the website is low. There is no DNSSEC enabled on the domain, no security headers detected, and no visible HTTPS confirmation from the data provided. No vulnerability disclosure or incident response information is present. The absence of privacy and cookie policies further indicates compliance gaps. The site does not collect user data or have forms, reducing attack surface but also limiting user engagement. Recommendations include enabling DNSSEC, implementing HTTPS with strong SSL/TLS, adding security headers, and publishing privacy and cookie policies to improve compliance and trust.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve domain security.
  2. Implement HTTPS with a valid SSL certificate and enforce HSTS to secure user connections.
  3. Add comprehensive privacy and cookie policies to comply with GDPR and inform users.
  4. Deploy standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Publish vulnerability disclosure and incident response contact information to enhance security transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
teamo
Description
Téamo was a hobby project providing telecommunication subscription services, now discontinued due to the founders focusing on other projects.
Key services
Telecommunication subscription packages
Content quality
basic
Branding
moderate

Technology

Stack
Jekyll, Anchor.js, AWS DNS
Frameworks
Jekyll
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
good

Security

Observed score
40/100

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 content indicates the service has been discontinued.
  2. No privacy, cookie, or terms of service policies found.
  3. Contact email provided is a personal/business email of the founder, not a company domain.
  4. No phone numbers or physical addresses provided.
  5. No security policies or incident response information present.
  6. Website uses Jekyll static site generator and AWS DNS services.
  7. No analytics or tracking scripts detected.
  8. No advertising or marketing tools detected.
  9. No forms or data collection mechanisms present.
  10. No social media links found on the page.
Technical notes

Notes

The website is built using the Jekyll static site generator, indicating a simple, lightweight infrastructure. Hosting is inferred to be on AWS due to DNS nameservers. The site uses minimal JavaScript, including Anchor.js for anchor link enhancements. No CMS beyond Jekyll is detected. Performance is likely moderate given static content and minimal assets. Mobile optimization and accessibility are basic but functional. SEO is supported by proper meta tags and JSON-LD structured data. There is no evidence of analytics or tracking scripts, which reduces privacy concerns but also limits marketing insights. The technical stack is modern but minimal, suitable for a small informational site rather than a complex business platform.
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 teamo.se. 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 teamo.se.

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.