Skip to main content

Security report for urmet.com

Medium risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

55/100

Risk levelMedium

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

Scanned

This is an earlier scan of urmet.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
58/ 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

5 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

This scan found 21 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
0
Security headers
25
Email security
70
DNS health
75
Network security
100
GDPR outside view
58
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 urmet.com, from OffSeq Breach.

Total records
2,806
Employees
5
Customers
2,794
Third parties
7
Weak passwords
13%

Latest record dated 2026-02-18 · 19 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for urmet.com.

Select it in the checkout above.

Masked preview

  • –urmet.com2026-02-18
  • –www.urmet.com2025-08-01
  • –urmet.com2025-07-25
  • –urmet.com2025-07-22
  • –www.urmet.com2025-07-20

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

URMET S.p.A. holds a strong market position in the security and communication technology sector, focusing on video door phones and intrusion alarm systems. The business model revolves around manufacturing and distributing these systems through professional channels and direct support to end-users. The company maintains active social media channels and a help desk, enhancing customer engagement and support. The presence of a code of ethics and certifications suggests a commitment to quality and compliance. The website content and structure support the company's professional image and market reach within Italy and internationally.

Security posture

The website demonstrates a good security posture with HTTPS enforced and a comprehensive cookie consent mechanism that respects user privacy and GDPR requirements. However, the absence of explicit security policies, incident response contacts, and security.txt files indicates room for improvement in transparency and readiness. No security headers were detected in the HTML content, which could enhance protection against common web vulnerabilities. No exposed sensitive data or vulnerable libraries were identified, suggesting a well-maintained technical environment.

Recommendations

  1. Implement and publish a dedicated security policy page detailing security practices and compliance.
  2. Add incident response contact information such as security@ or abuse@ email addresses to facilitate vulnerability reporting.
  3. Deploy standard security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), X-Frame-Options, and X-Content-Type-Options.
  4. Consider publishing a security.txt file to improve vulnerability disclosure transparency.
  5. Regularly audit and update third-party libraries to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Legal name
URMET S.p.A.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
URMET S.p.A.
Description
Leading company specialized in the development of systems, video door phone, telephone and anti-intrusion systems in residential, tertiary and industrial sectors.
Key services
Video door phone systems, Telephone systems, Anti-intrusion systems, Help Desk support, Commercial network
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.5.1, jQuery Migrate 3.4.0, jQuery UI 1.13.2, Bootstrap, Swiper, Slick Carousel
Frameworks
ASP.NET Web Forms
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced (canonical link is https)
  • Cookie consent banner with granular controls
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
CookiePro
Marketing tools
CookiePro Consent Management
Transparency
good

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges
  2. Cookie consent mechanism is implemented with granular user controls
  3. Business information is clearly presented with physical address and social media links
  4. No explicit security policy or incident response contacts found
  5. Website uses a mature CMS (DNN) and common JS libraries
  6. No exposed sensitive data or obvious vulnerabilities detected in HTML content
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

Earlier scans of this domain

  1. 73/100Medium30 findingsView report
Reviews of this site

Share your experience with urmet.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 urmet.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.