Skip to main content

Security report for portaljuragan.io

Other · United States

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

57/100

Risk levelMedium

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

The website portaljuragan.io currently presents no accessible content, with an empty HTML body and no metadata, scripts, or forms. The domain is registered with Dynadot Inc and uses Cloudflare nameservers, but DNSSEC is not enabled. Notably, the domain creation date is set in the future (March 26, 2025), which is inconsistent and suspicious. There are no privacy, cookie, or terms of service policies available, nor any contact information or business details on the site. This lack of content and transparency severely limits the ability to assess the business or its market position. Technically, the site shows minimal security posture with no security headers and basic SSL configuration. The site appears to be either blocked by a WAF or under construction.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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

9 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

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

Keep watching portaljuragan.io

This scan found 27 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
57
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
40
Average
57

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 portaljuragan.io, from OffSeq Breach.

No leaked records found

Breach holds no records for portaljuragan.io 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 absence of website content and business information, no meaningful business intelligence can be derived. The domain is newly registered (or with a suspicious future date), and no evidence of market positioning, services, or partnerships is available. The registrant is located in the US, but no company name or branding is present on the site. The lack of contact details and policies further reduces credibility and trust.

Security posture

The security posture is weak. The site uses HTTPS but lacks DNSSEC and security headers. No incident response or vulnerability disclosure information is present. The domain registration data is suspicious due to the future creation date. No privacy or cookie compliance mechanisms are implemented. Overall, the site is at risk of trust and security issues, and no best practices are observed.

Recommendations

  1. Verify and correct the domain registration date to reflect accurate information.
  2. Develop and publish comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  3. Add clear contact information and business details to improve credibility and user trust.
  4. Implement security headers and enable DNSSEC to enhance domain and website security.
  5. Populate the website with meaningful content and metadata to improve SEO, user experience, and business communication.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Minimal HTML content with empty body and Cloudflare nameservers indicate possible WAF or security challenge blocking content. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
30/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 completely empty (empty HTML body).
  2. No metadata, no scripts, no forms, no links detected.
  3. Domain uses Cloudflare nameservers but no DNSSEC enabled.
  4. WHOIS data shows domain created in the future, which is likely erroneous or suspicious.
  5. No privacy, cookie, or terms of service policies found.
  6. No contact information or business details available on the site.
  7. Security posture is minimal with no security headers or advanced SSL configuration.
  8. Website is likely blocked or under construction with no accessible content.
Technical notes

Notes

The website currently has an empty HTML structure with no metadata, scripts, or visible content. The domain uses Cloudflare for DNS but does not enable DNSSEC, which is a missed security opportunity. No CMS or frameworks are detected. Performance and mobile optimization cannot be assessed due to lack of content. The site likely suffers from technical debt or is in an early development phase. The suspicious WHOIS data further complicates trust in the technical setup.
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 portaljuragan.io. 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 portaljuragan.io.

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.