Skip to main content

Security report for getnametags.com

Warmly · Technology · N/a

Medium risk. 4 critical or high findings in Security headers and GDPR outside view.

Security score

71/100

Risk levelMedium

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

Warmly is a technology company specializing in virtual nametags designed to enhance professionalism and engagement in video meetings, particularly through Zoom integration. The company targets professionals across various sectors including sales, marketing, consulting, and finance, offering customizable virtual nametags and related meeting enhancement tools. The website is well-designed, content-rich, and provides clear navigation and branding consistency, positioning Warmly as a reputable player in the virtual meeting enhancement market. Technically, the site is built on Webflow CMS, hosted with Cloudflare DNS, and uses modern marketing and analytics tools such as PostHog and OneTrust for cookie consent. However, the site suffers from a critical security issue: the absence of a valid SSL certificate and HTTPS support, which significantly impacts its security posture and trustworthiness. Privacy compliance is strong with comprehensive policies and consent mechanisms in place. Overall, the site demonstrates good digital maturity but requires urgent security improvements to protect user data and enhance trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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

4 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 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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • 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

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

Keep watching getnametags.com

This scan found 20 issues across 5 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
100
Security headers
30
Email security
75
DNS health
80
Network security
100
GDPR outside view
43
Average
71

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

Warmly operates a SaaS business model focused on enhancing virtual meeting experiences through branded nametags and meeting tools. Its market positioning leverages integrations with major platforms like Zoom, targeting professionals who value personalization and engagement in remote communications. The company showcases strong branding and customer testimonials, indicating a growing user base and positive market reception. The presence of a dedicated security site and comprehensive privacy policies reflects a mature approach to compliance and user trust. The ecosystem includes partnerships with Zoom Marketplace and uses third-party services for analytics and consent management. Growth indicators include active marketing, social media presence, and enterprise offerings. Strategic observations suggest Warmly is focused on expanding its footprint in the virtual collaboration space with a strong emphasis on user experience and compliance.

Security posture

The current security posture of the website is moderate to poor due to the lack of a valid SSL certificate and HTTPS enforcement, exposing users to potential data interception risks. While DNS records show proper SPF and DMARC configurations, the absence of TLS protocols and security headers weakens the overall security framework. The site employs cookie consent mechanisms compliant with GDPR, indicating awareness of privacy regulations. No direct incident response contacts or vulnerability disclosure policies were found, which could hinder timely handling of security events. The use of Cloudflare DNS provides some resilience, but the missing HTTPS is a critical vulnerability. Recommendations include immediate SSL certificate installation, enabling modern TLS versions, and implementing security headers and best practices to improve protection and user trust.

Recommendations

  1. Install and enforce a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable insecure protocols.
  3. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security with preload.
  4. Establish and publish a vulnerability disclosure policy and provide incident response contact information.
  5. Enhance site performance by optimizing resource loading to reduce page load times.
  6. Maintain and update privacy and cookie policies regularly to ensure ongoing GDPR compliance.
  7. Increase transparency by providing clear business contact information on the website.
  8. Conduct regular security audits and penetration testing to identify and remediate vulnerabilities.
  9. Improve accessibility features to ensure compliance with standards and enhance user experience.
  10. Leverage certificate transparency logs to monitor SSL certificate issuance and prevent misuse.
Technical notes

Notes

The website is built using Webflow CMS, leveraging Cloudflare for DNS services and content delivery. It integrates third-party analytics (PostHog) and cookie consent management (OneTrust), indicating a modern marketing and compliance infrastructure. The site includes JavaScript libraries such as Tippy.js and Popper.js for UI enhancements. Performance metrics indicate a slow load time (~14 seconds) and a large page size (~1.2MB), suggesting opportunities for optimization. Mobile responsiveness and accessibility are well addressed. However, the lack of a valid SSL certificate and disabled TLS protocols represent significant technical risks. The DNS setup is robust with SPF and DMARC records configured correctly. Overall, the technical infrastructure supports a professional web presence but requires urgent security and performance improvements to align with best practices.
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 getnametags.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 getnametags.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.