Adler Historic Guesthouse is a hospitality business located in Brixen, Italy, offering guesthouse accommodation services. The website is professionally designed using TYPO3 CMS and modern web technologies, providing a good user experience with mobile optimization and clear navigation. The business has a positive market position supported by strong customer ratings and active social media presence. However, the domain WHOIS data is missing or unavailable, which raises concerns about registration transparency. Security posture is generally good with HTTPS enabled, but lacks some security headers and formal privacy and cookie policies. Overall, the website is trustworthy and functional but would benefit from improved compliance and transparency.
Scanned ·
NIS2 and GDPR posture
GDPR outside view
53/ 100 · Medium
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
7 findings rated critical or high. Fix these first.
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"
This scan found 23 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. The full timeline opens with your unlock code.
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
82
Security headers
25
Email security
80
DNS health
85
Network security
20
GDPR outside view
53
Average
58
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 adlerbrixen.com, from OffSeq Breach.
No leaked records found
Breach holds no records for adlerbrixen.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
The business targets travelers seeking historic and quality accommodation in Brixen. It operates a small-scale hospitality model focused on guesthouse services. The website content and social media links indicate a well-established presence in the local hospitality market. There is no evidence of parent or subsidiary companies. The business leverages digital marketing tools such as newsletter subscriptions but does not appear to use extensive tracking or advertising networks. Growth potential could be enhanced by improving privacy compliance and security transparency.
Security posture
The website enforces HTTPS and avoids exposing sensitive data in its HTML content. However, it lacks important security headers such as Content-Security-Policy and X-Frame-Options, which could improve protection against common web attacks. No vulnerability disclosures or incident response contacts are provided, limiting the ability to report security issues. The absence of privacy and cookie policies also indicates compliance gaps with GDPR and related regulations. Overall, the security maturity is moderate but can be improved with standard best practices.
Recommendations
Implement and publish a comprehensive privacy policy and cookie consent mechanism to enhance GDPR compliance.
Add standard security headers including Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
Publish a security.txt file or vulnerability disclosure policy with contact information for incident reporting.
Improve accessibility features to meet WCAG guidelines for broader user inclusivity.
Clarify domain registration details or use a registrar that provides transparent WHOIS data to improve trust.
Website is fully accessible with no blocking or WAF challenge.
Content is professionally presented and relevant to hospitality.
No explicit privacy or cookie policies found on main page.
WHOIS data is missing or domain is unregistered in public WHOIS.
Uses TYPO3 CMS with modern frontend technologies.
Contact information is present and consistent with business.
No visible security.txt or incident response info.
No advertising or tracking networks detected beyond newsletter widget.
Technical notes
Notes
The website uses TYPO3 CMS, a robust open-source content management system, combined with modern frontend libraries such as Swiper and Lightgallery for interactive elements. The site preloads fonts and images for performance optimization and uses a newsletter subscription script from Brandnamic. The site is mobile responsive and SEO optimized with proper meta tags and structured data (JSON-LD). Hosting provider details are not explicitly found. Performance is moderate with room for improvement in loading speed and accessibility compliance.
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 adlerbrixen.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review adlerbrixen.com.