Skip to main content

Security report for unicreditlife.it

Finance · N/a

Medium risk. 7 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

65/100

Risk levelMedium

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

The website unicreditlife.it is currently inaccessible due to a security or WAF blocking mechanism, as evidenced by the 'Access Denied' error page served via Akamai's edgesuite.net. This prevents any meaningful content or metadata extraction, severely limiting the ability to analyze the business or technical infrastructure. The WHOIS data is suspicious, showing a domain creation date in the future (January 27, 2025), which undermines trust and legitimacy. DNSSEC is enabled, which is a positive security indicator. Overall, the website appears to be related to the finance sector but lacks accessible information to confirm business details or services. The security posture is limited to DNSSEC and HTTPS, with no visible security headers or policies. Due to the blocking, the AI score is low, reflecting the inability to perform a full assessment.

Scanned

NIS2 and GDPR posture

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

7 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

  2. 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';…

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

Keep watching unicreditlife.it

This scan found 22 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
82
Security headers
30
Email security
85
DNS health
70
Network security
100
GDPR outside view
25
Average
65

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

Due to the lack of accessible content, no detailed business intelligence can be derived. The domain name suggests affiliation with the finance sector, possibly insurance or banking services. The domain age and WHOIS inconsistencies raise concerns about legitimacy or data accuracy. No contact information, policies, or certifications are available to assess market positioning or competitive advantages. The hosting via Akamai indicates use of a major CDN and security provider, which is common for enterprise-level finance websites.

Security posture

The website benefits from DNSSEC and HTTPS, indicating basic security hygiene. However, the absence of visible security headers, policies, or incident response information limits the security maturity assessment. The presence of a WAF or security blocking mechanism is confirmed, which protects the site but also restricts content access. The suspicious WHOIS data further reduces trust. No vulnerabilities or exposed sensitive data are observable due to content blocking. Compliance with GDPR or other frameworks cannot be verified.

Recommendations

  1. Verify and correct WHOIS domain registration data to reflect accurate creation date and registrant information.
  2. Ensure website content is accessible to legitimate users while maintaining security protections to allow proper analysis and user experience.
  3. Implement and publish comprehensive privacy, cookie, security, and incident response policies to improve transparency and compliance.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance security posture.
  5. Provide clear contact information and business details on the website to improve trust and credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Access Denied page with minimal HTML content and reference to Akamai edgesuite.net error URL indicates a WAF or security blocking mechanism. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Security

Observed score
30/100
Good practices seen
  • DNSSEC enabled

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is completely blocked by a WAF or security mechanism.
  2. No meaningful content or metadata available for analysis.
  3. WHOIS data contains suspicious future creation date.
  4. No contact, policy, or business information is accessible.
  5. Website hosted behind Akamai CDN with security filtering.
  6. No scripts, forms, or external links except error reference domain.
  7. No privacy or cookie policies detected.
  8. No security policies or incident response information found.
  9. No analytics or advertising technologies detected.
  10. Content safety is safe due to lack of content.
Technical notes

Notes

The website is hosted behind Akamai's CDN and security platform, as indicated by the edgesuite.net error reference. No CMS, frameworks, or scripts are detectable due to content blocking. DNSSEC is enabled, and HTTPS is presumably enforced. Performance, mobile optimization, accessibility, and SEO cannot be assessed. The technical infrastructure appears to rely on enterprise-grade CDN and security services but lacks visible frontend implementation details due to the WAF block.
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 unicreditlife.it. 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 unicreditlife.it.

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.