The website at thomasgroup.com currently serves as a minimal placeholder or parking page with very limited content. There is no visible business information, contact details, or policies that would indicate an active commercial or organizational presence. The site loads external scripts primarily related to Google Adsense and a parking-lander service, suggesting it is not actively maintained for business purposes. The technical infrastructure is minimal, with basic JavaScript usage and no detected CMS or advanced frameworks. Security posture is weak due to lack of HTTPS information, absence of security headers, and no privacy or cookie policies. Overall, the site presents a low trust profile and does not provide sufficient information to assess business legitimacy or compliance.
Scanned ·
NIS2 and GDPR posture
GDPR outside view
25/ 100 · Critical
Checks completed
7of 7
NIS2 Art. 21(2)
a(a) Risk analysis and security policies: Not visible from outside
b(b) Incident handling: One indicator
c(c) Business continuity, backups and crisis management: Not visible from outside
d(d) Supply chain security: Not visible from outside
e(e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
f(f) Assessing the effectiveness of security measures: Not visible from outside
g(g) Cyber hygiene and security training: Not visible from outside
h(h) Cryptography and encryption: Partly checked
i(i) HR security, access control and asset management: One indicator
j(j) Multi-factor authentication and secured communications: Not visible from outside
Partly checked
One indicator
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
8 findings rated critical or high. Fix these first.
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
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"
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.
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
70
DNS health
75
Network security
100
GDPR outside view
25
Average
48
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 thomasgroup.com, from OffSeq Breach.
No leaked records found
Breach holds no records for thomasgroup.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.
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 content and business information, it is not possible to determine the market positioning, business model, or target audience of the entity behind thomasgroup.com. No competitive advantages, revenue streams, or partnership ecosystems are evident. The domain appears to be either unused or reserved without active business operations. No growth indicators or strategic insights can be derived from the current website state.
Security posture
The security posture of the website is minimal and potentially risky. There is no evidence of HTTPS enforcement or security headers, which are critical for protecting user data and preventing common web attacks. The absence of privacy and cookie policies indicates non-compliance with GDPR and other data protection regulations. No incident response or vulnerability disclosure information is provided, suggesting a lack of security governance. The site does not collect user data via forms, which reduces exposure but also limits functionality. Overall, the security maturity is very low.
Recommendations
Implement HTTPS with a valid SSL/TLS certificate to secure all communications.
Add comprehensive privacy and cookie policies to comply with GDPR and other regulations.
Provide clear contact information including email and phone to improve business credibility.
Incorporate security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
Develop meaningful website content and navigation to enhance user experience and SEO.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
Content quality
poor
Branding
inconsistent
Technology
Stack
JavaScript
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor
Security
Observed score
30/100
Analytics and tracking
Tracking level
minimal
Privacy practices
poor
Advertising
Ad networks
Google Adsense
Transparency
poor
Site quality
Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low
Key observations
Website content is minimal and appears to be a placeholder or parking page.
No meaningful business or contact information is present.
No privacy, cookie, or terms of service policies found.
Only external scripts are from Google Adsense and wsimg.com for parking-lander resources.
No forms or user input fields detected.
No social media or contact links present.
No security headers or HTTPS information available from provided data.
Website lacks SEO and accessibility features.
No WHOIS data provided to verify domain legitimacy.
Technical notes
Notes
The website uses minimal JavaScript and loads external scripts from Google Adsense and a parking-lander service. There is no detected CMS or modern web framework. The HTML is basic with no meta tags for SEO or accessibility features. Performance is likely moderate due to minimal content but lacks optimization. Mobile responsiveness is basic, and no accessibility standards are evident. The technical debt is high due to lack of essential web standards and security practices. Modernization opportunities include adopting HTTPS, improving content structure, and implementing SEO and accessibility 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.
Reviews of this site
Share your experience with thomasgroup.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review thomasgroup.com.