Skip to main content

Security report for progettocresco.it

Other · Italy

High risk. 16 critical or high findings in GDPR outside view, Network security and 4 other checks.

Security score

40/100

Risk levelHigh

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

The website progettocresco.it currently displays a 403 Forbidden error page, indicating that access to the content is blocked or restricted. There is no accessible business information, contact details, or policy documents available on the site. The domain is registered since 2011 and appears legitimate in terms of registration age and status, but the lack of accessible content severely limits the ability to assess the business or technical maturity. The technical infrastructure is minimal, using basic HTML and CSS with Google Fonts, and no advanced frameworks or CMS are detected. Security posture is weak due to absence of HTTPS information and security headers. Privacy compliance is non-existent as no privacy or cookie policies are found. Overall, the site is currently non-functional for end users and lacks critical trust and security indicators.

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

16 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

  2. 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: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL 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

  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 progettocresco.it

This scan found 33 issues across 7 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
72
Security headers
35
Email security
70
DNS health
50
Network security
0
GDPR outside view
10
Average
40

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 progettocresco.it, from OffSeq Breach.

No leaked records found

Breach holds no records for progettocresco.it 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 blocked content, no detailed business intelligence can be derived. The domain age suggests an established entity, possibly a small business or project based in Italy. No information on market positioning, services, or partnerships is available. The lack of contact information and policies indicates low business transparency and credibility at this time.

Security posture

The security posture is poor. The site does not present HTTPS or security headers, and no incident response or vulnerability disclosure information is available. The 403 error may be due to server configuration or access restrictions but does not indicate a WAF challenge. There is no evidence of compliance with GDPR or other security frameworks. The site is vulnerable to trust issues due to lack of visible security best practices.

Recommendations

  1. Enable HTTPS with a valid SSL certificate to secure communications.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish privacy and cookie policies to comply with GDPR and inform users.
  4. Provide clear contact information including emails and phone numbers for business and security incident response.
  5. Investigate and resolve the 403 Forbidden error to restore website accessibility.
  6. Add accessibility and SEO improvements to enhance user experience and search visibility.
  7. Consider adding vulnerability disclosure and security.txt files to improve security transparency.
  8. Regularly audit and update website content and technical stack to maintain professionalism and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error page indicating access is blocked or forbidden. No WAF vendor-specific challenge detected. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
moderate

Technology

Stack
HTML5, CSS3, Google Fonts
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
10/100

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 content is inaccessible due to 403 Forbidden error.
  2. No business or contact information is available on the page.
  3. No privacy, cookie, or terms of service policies found.
  4. No forms or data collection mechanisms present.
  5. Minimal external resources used (Google Fonts).
  6. No analytics or tracking scripts detected.
  7. No security headers or HTTPS information available.
  8. Domain is registered and active but website is currently blocked.
Technical notes

Notes

The website uses basic HTML5 and CSS3 with Google Fonts for typography. No JavaScript libraries, frameworks, or CMS platforms are detected. The page is a static error page with no dynamic content or forms. Performance is moderate given the minimal content, but mobile optimization and accessibility are basic at best. The lack of HTTPS and security headers is a significant technical deficiency. Hosting provider and infrastructure details are not discernible from the content. Overall, the technical implementation is minimal and requires modernization and security enhancements.
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 progettocresco.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 progettocresco.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.