Skip to main content

Security report for gobankingrates.com

Other · N/a

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

Security score

69/100

Risk levelMedium

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

The website www.gobankingrates.com is currently inaccessible due to an Amazon CloudFront Web Application Firewall (WAF) configuration that blocks access from the querying country, resulting in a 403 error page. This prevents any meaningful content, metadata, or technical details from being retrieved or analyzed. The WHOIS lookup for the domain failed to return any registration data, indicating either the domain is unregistered, expired, or protected by privacy mechanisms that obscure registrar and registrant information. Consequently, no business, contact, or security policy information is available. From a technical perspective, the site is hosted behind Amazon CloudFront, but no further details on CMS, frameworks, or technologies can be determined due to the lack of accessible content. Security posture cannot be assessed as no security headers or SSL configuration details are available. Privacy compliance and business credibility cannot be evaluated without access to policies or contact information. Overall, the site presents a high risk due to inaccessibility and lack of verifiable registration data. This severely limits trust and raises questions about legitimacy. Strategic recommendations include resolving WAF blocking issues to enable access, publishing clear WHOIS and business information, implementing security best practices, and providing transparent privacy and contact policies.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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. 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';…

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

    • 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

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

Keep watching gobankingrates.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
82
Security headers
15
Email security
82
DNS health
85
Network security
100
GDPR outside view
50
Average
69

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 absence of accessible content and WHOIS data, no reliable business intelligence can be derived. The domain appears to be either unregistered or protected, which is inconsistent with a legitimate, operational business website. No information about market positioning, revenue streams, partnerships, or customer segments is available. The lack of accessible content and metadata suggests the site is either offline, misconfigured, or restricted, preventing any competitive or operational insights.

Security posture

The security posture cannot be fully assessed due to the site's inaccessibility. The presence of an Amazon CloudFront WAF blocking access indicates some level of security control, but it also prevents legitimate analysis. No security headers or SSL details are visible, and no incident response or vulnerability disclosure information is available. The absence of WHOIS data further complicates trust assessment. Overall, the security maturity appears low or unknown, with critical gaps in transparency and accessibility.

Recommendations

  1. Resolve the CloudFront WAF configuration to allow legitimate access and enable full site analysis.
  2. Ensure WHOIS registration data is complete, accurate, and publicly available to improve trust.
  3. Implement and publish comprehensive privacy, cookie, and security policies to demonstrate compliance.
  4. Add security headers and enforce HTTPS to strengthen security posture.
  5. Provide clear contact and incident response information to enhance transparency and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

CloudFront detected. Amazon CloudFront distribution is configured to block access from your country, resulting in a 403 error page. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

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 inaccessible due to CloudFront WAF blocking
  2. No metadata, scripts, forms, or external links available for analysis
  3. WHOIS data is missing or domain appears unregistered
  4. No contact or policy information found
  5. No security headers or SSL information available
  6. Unable to assess business or technical details due to lack of content
Technical notes

Notes

The technical infrastructure is largely unknown due to the site's inaccessibility. Hosting is via Amazon CloudFront, but no CMS, frameworks, or scripts are detectable. The site returns a 403 error with a CloudFront block message, indicating restrictive access controls. No metadata, SEO tags, or performance indicators are available. This lack of accessible technical data suggests either a misconfiguration or intentional geo-blocking that limits usability and analysis.
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

Earlier scans of this domain

  1. 70/100Medium28 findingsView report
Reviews of this site

Share your experience with gobankingrates.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 gobankingrates.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.