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

70/100

Risk levelMedium

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

The website www.gobankingrates.com is currently inaccessible due to geographic blocking enforced by Amazon CloudFront, resulting in a 403 Forbidden error. This prevents any meaningful content or metadata extraction, severely limiting the ability to analyze the business, technical infrastructure, or security posture. The WHOIS lookup failed to return any registration data, indicating either the domain is unregistered, privacy protected, or there is a data retrieval issue. Consequently, no registrant or domain age information is available, raising concerns about legitimacy and trustworthiness. From a technical perspective, the site is hosted behind Amazon CloudFront, which is actively blocking access from the querying location. No scripts, forms, or external links were visible in the provided HTML snippet. Without access to the actual website content, no assessment of SEO, accessibility, or performance can be made. Security headers and SSL configuration cannot be evaluated. The security posture is effectively unknown due to the lack of access. No privacy, cookie, or terms of service policies were found, nor any contact or incident response information. The absence of WHOIS data and the blocking mechanism lowers the trust score significantly. Overall, the site cannot be reliably assessed in its current state, and the risk of suspicious or malicious activity cannot be ruled out without further data. Strategic recommendations include resolving the geographic blocking to allow legitimate access, publishing clear privacy and security policies, and ensuring WHOIS data is properly registered and publicly available to improve trust and compliance.

Scanned

This is an earlier scan of gobankingrates.com. View the latest report

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 19 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
87
DNS health
85
Network security
100
GDPR outside view
50
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

Due to the lack of accessible content and WHOIS data, no detailed business intelligence can be derived. The domain appears to be related to financial content based on its name, but no direct evidence or business details are available. The absence of registrant information and domain age data prevents validation of market position, competitive advantages, or partnership ecosystems. No revenue streams or customer segments can be identified. The domain's current state suggests it is either inactive, misconfigured, or restricted, limiting any meaningful business insights.

Security posture

The security posture cannot be fully assessed due to the site's inaccessibility. The presence of Amazon CloudFront as a hosting and distribution provider indicates some level of infrastructure robustness. However, the geographic blocking may be a security control or misconfiguration. No security headers or SSL details are visible. The lack of privacy and incident response information suggests compliance gaps. Without access to the site, potential vulnerabilities or data protection practices cannot be evaluated. The WHOIS data absence further complicates trust and legitimacy assessments.

Recommendations

  1. Resolve geographic blocking to enable legitimate user access and allow security and content analysis.
  2. Ensure domain registration information is complete, accurate, and publicly available to improve trust.
  3. Publish comprehensive privacy, cookie, and terms of service policies to meet compliance requirements.
  4. Implement and expose security headers and HTTPS to enhance security posture.
  5. Provide clear contact and incident response channels to improve transparency and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

CloudFront detected. The 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
Branding
inconsistent

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 inaccessible due to CloudFront geographic blocking.
  2. No metadata, structured data, or visible content to analyze.
  3. No contact or policy pages accessible.
  4. WHOIS data unavailable, indicating possible unregistered domain or privacy protection.
  5. Security posture cannot be assessed due to lack of access.
  6. No external links or scripts detected in the provided HTML.
  7. Website is currently non-functional for analysis purposes.
Technical notes

Notes

The website is hosted behind Amazon CloudFront, which is currently blocking access from the querying location. No HTML content beyond a 403 error page is available, preventing analysis of the technology stack, CMS, or frameworks. No scripts or external resources are loaded in the provided HTML snippet. The lack of WHOIS data and domain registration details suggests possible domain registration issues or privacy protection. Performance, mobile optimization, and SEO cannot be assessed. The technical infrastructure appears minimal or misconfigured given the blocking behavior.
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. 69/100Medium29 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.