Skip to main content

Security report for guard-core.com

Guard Core · Technology · N/a

Medium risk. 4 critical or high findings in Security headers, Email security and 1 other check.

Security score

70/100

Risk levelMedium

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

Guard Core presents itself as a security monitoring dashboard focused on application-layer security and API protection. The website is built using modern technologies such as React and Next.js and is hosted behind Cloudflare DNS services. However, the site is currently non-functional, returning a 500 error with a JavaScript exception, which severely impacts user experience and trust. The domain is very new, created in April 2026, which aligns with the futuristic content dates but suggests the business is in an early or staging phase. Privacy and cookie policies are present with consent mechanisms, indicating some compliance awareness, but no contact or security policy information is visible. Overall, the business appears to be a small technology company targeting developers and organizations needing advanced application-layer security solutions.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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

4 findings rated critical or high. Fix these first.

  1. 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

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

    • High

      No DMARC record found

      DMARC provides email authentication and reporting

      What to do: Add DMARC record: "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching guard-core.com

This scan found 20 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
37
Security headers
65
Email security
50
DNS health
85
Network security
100
GDPR outside view
83
Average
70

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

The company operates in the technology sector, specifically focusing on security monitoring and API protection. Its market positioning is niche, targeting modern application-layer threats with a security dashboard product. The business model likely revolves around software or SaaS offerings for security analytics. There is no evidence of partnerships, subsidiaries, or parent companies. The lack of contact information and minimal content suggests early-stage operations or a placeholder site. The company emphasizes modern security challenges such as AI-coordinated attacks and advanced API security, indicating a forward-looking approach.

Security posture

The security posture is moderate but impaired by the website's current non-functionality and lack of DNSSEC. HTTPS is enforced, and domain status flags prevent unauthorized transfers or deletions, which are positive indicators. However, the absence of security headers and visible security policies, combined with a broken site, reduces the overall security maturity. No incident response contacts or vulnerability disclosure mechanisms are present. The site uses Cloudflare DNS but does not leverage DNSSEC, which is recommended. The presence of a cookie consent mechanism aligns with privacy best practices.

Recommendations

  1. Resolve the server-side error causing the 500 response to restore website functionality.
  2. Enable DNSSEC to enhance domain security and trust.
  3. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Publish clear security policies and incident response contact information on the website.
  5. Add terms of service and vulnerability disclosure pages to improve transparency and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Website returns a 500 error page with Cloudflare DNS and references to Cloudflare challenge scripts. The page shows a JavaScript error and no functional content. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Company
Guard Core
Description
Security monitoring dashboard
Key services
Security monitoring dashboard, Application-layer security insights, API security analytics
Content quality
basic
Branding
moderate

Technology

Stack
React, Next.js, Cloudflare DNS, JavaScript
Frameworks
Next.js, React
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • HTTPS enforced
  • Domain status includes clientDeleteProhibited and clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is currently non-functional showing a 500 error with JavaScript issues.
  2. Uses Cloudflare DNS but no DNSSEC enabled.
  3. Privacy and cookie policies are present with consent mechanism.
  4. No contact information or security policies visible on the site.
  5. No terms of service or vulnerability disclosure found.
  6. Technical stack is modern but site lacks content and polish.
  7. No advertising or analytics services detected.
  8. Domain WHOIS data is public but domain is very new and possibly a staging site.
Technical notes

Notes

The website uses a modern React and Next.js stack with Cloudflare DNS hosting. Preloading of fonts and images is implemented, indicating some performance optimization efforts. However, the site currently fails to render properly due to a JavaScript error, impacting user experience and SEO. No CMS is detected, suggesting a custom or static site approach. Mobile optimization and accessibility are basic but present. SEO meta tags and Open Graph tags are included but limited. No analytics or advertising scripts are detected, indicating minimal tracking or marketing tools in use. The domain is protected against unauthorized transfer and deletion but lacks DNSSEC. Overall, the technical infrastructure is modern but immature and incomplete.
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 guard-core.com. 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 guard-core.com.

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.