Skip to main content

Security report for gpborg.com

GPWORKS · Other · N/a

High risk. 11 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

27/100

Risk levelHigh

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

The website for gpborg.com currently serves as a minimal coming soon or maintenance placeholder page branded as GPWORKS. The content is extremely limited, with no descriptive business information, contact details, or policies. The site references a different domain (gpworks.mt) in metadata and resource links, indicating possible domain transition or misconfiguration. The technical infrastructure is based on WordPress with a coming soon plugin, using external resources such as Font Awesome and Google Fonts. However, the site lacks HTTPS on referenced resources and does not implement visible security headers or privacy compliance mechanisms. The subscription form is basic and lacks advanced security features like CAPTCHA. Overall, the site exhibits low digital maturity and minimal business presence online.

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

      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. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  4. 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"

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

Keep watching gpborg.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
0
Security headers
15
Email security
55
DNS health
80
Network security
0
GDPR outside view
10
Average
27

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 · found on this site
  • 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 gpborg.com, from OffSeq Breach.

No leaked records found

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

Due to the lack of business information, no clear market positioning, business model, or target audience can be identified. The site appears to be in early development or a placeholder state. There are no visible partnerships, certifications, or trust indicators. The domain uses privacy protection in WHOIS, which is common for early-stage or non-public businesses. The absence of contact information and policies limits credibility and trustworthiness.

Security posture

The security posture is weak, with no HTTPS enforced on external resources, no security headers detected, and no visible incident response or security policies. The subscription form uses POST with same-origin credentials but lacks anti-bot protections. No vulnerabilities are explicitly visible, but the lack of HTTPS and security best practices exposes the site to risks. No GDPR or privacy compliance measures are evident.

Recommendations

  1. Implement HTTPS across the entire website and all external resources to ensure secure communication.
  2. Add comprehensive privacy and cookie policies to comply with GDPR and build user trust.
  3. Provide clear contact information and business details to improve credibility.
  4. Enhance form security by adding CAPTCHA or other anti-bot mechanisms.
  5. Deploy security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
GPWORKS
Content quality
poor
Branding
moderate

Technology

Stack
WordPress, CMP Coming Soon Maintenance Plugin, Font Awesome, Google Fonts
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
40/100
Good practices seen
  • No visible exposed sensitive data
  • Form uses fetch with POST and same-origin credentials

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 is a coming soon/maintenance placeholder page with minimal content.
  2. Main domain referenced in metadata and resources is gpworks.mt, not gpborg.com.
  3. No privacy, cookie, or terms of service policies found.
  4. No contact information or business details provided.
  5. No visible security headers or HTTPS usage on external resources.
  6. Form present but only for subscription with minimal fields and no CAPTCHA.
  7. No social media or phone contact information found.
  8. Website uses WordPress with a coming soon plugin.
  9. No analytics or tracking scripts detected.
  10. No structured data (JSON-LD) present.
Technical notes

Notes

The site is built on WordPress using a coming soon maintenance plugin, with external CSS and JS resources loaded over HTTP, which is insecure. The HTML is valid but minimal, with no structured data or SEO-rich content. Performance is moderate due to minimal content but could be improved with HTTPS and optimized resource loading. Mobile optimization and accessibility are basic, with no advanced features detected. The site lacks analytics or tracking tools, indicating low digital marketing maturity.
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 gpborg.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 gpborg.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.