Skip to main content

Security report for firsttexasbank.net

First Texas Bank · Finance · United States

Medium risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

68/100

Risk levelMedium

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

First Texas Bank operates as a regional community bank serving multiple Texas locations with a focus on personal and business banking services including lending and mortgage solutions. The website presents a professional and consistent brand image with clear navigation and a secure online banking login portal. The technical infrastructure is based on WordPress CMS with modern web technologies such as Bootstrap and jQuery, supported by caching mechanisms to optimize performance. Security posture is strong with HTTPS enforced and secure form handling, though the absence of security headers and visible privacy or cookie policies indicates room for improvement. Overall, the site is trustworthy and well-positioned for its target audience but would benefit from enhanced compliance and security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 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

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

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: Google APIs

      What to do: Document all third-party data sharing in your privacy policy

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

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

Keep watching firsttexasbank.net

This scan found 21 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
47
Security headers
85
Email security
70
DNS health
70
Network security
100
GDPR outside view
35
Average
68

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 bank targets local Texas residents and businesses, offering a traditional banking model with digital enhancements. Its multiple branch locations and FDIC insurance provide competitive advantages in trust and accessibility. The business model relies on retail and commercial banking revenue streams, with digital banking services supporting customer convenience. The lack of visible contact information on the homepage suggests a focus on branch visits or secure portals for customer interaction. The partnership ecosystem is not explicitly detailed, and no related domains or subsidiaries were identified. Growth indicators include a modern website and multiple branch locations, but further data would be needed for deeper financial insights.

Security posture

The website demonstrates a mature security posture with HTTPS and secure login forms. However, the absence of key security headers such as Content-Security-Policy and Strict-Transport-Security reduces defense-in-depth. No vulnerabilities or exposed sensitive data were detected in the HTML content. The lack of published security policies, incident response contacts, or vulnerability disclosure mechanisms limits transparency and preparedness visibility. Compliance with privacy regulations such as GDPR is not evident, and cookie consent mechanisms are missing. Overall, the security culture appears cautious but could be enhanced by formalizing policies and improving technical controls.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies with user consent mechanisms to improve compliance and transparency.
  2. Add essential security headers (CSP, HSTS, X-Content-Type-Options, X-Frame-Options) to strengthen browser security.
  3. Publish security and incident response policies including contact channels for reporting security issues.
  4. Introduce a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Enhance accessibility features and provide clear contact information to improve user trust and experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
First Texas Bank
Description
First Texas Bank is a financial institution providing banking services including personal banking, business banking, lending, mortgage services, and digital banking solutions primarily serving Texas communities.
Key services
Personal Banking, Business Banking, Business Lending, Personal Lending, Mortgage Center, Digital Banking Services
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Bootstrap 4, Font Awesome, Google Fonts, W3 Total Cache
Frameworks
Bootstrap
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure login form with POST method and autocomplete off

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges
  2. No explicit privacy, cookie, or terms of service policies found on the homepage or linked pages
  3. Secure login form present for online banking with proper POST method and autocomplete disabled
  4. No contact emails or phone numbers explicitly listed on the homepage content
  5. Multiple branch locations visually presented with images and location names
  6. Use of modern web technologies and CMS (WordPress) with caching enabled
  7. No visible security headers detected in provided data
  8. No analytics or tracking scripts detected in the HTML content
  9. No social media links found in the provided HTML content
  10. No security.txt or vulnerability disclosure information found
Technical notes

Notes

The website is built on WordPress with Bootstrap 4 and jQuery, leveraging Google Fonts and Font Awesome for styling and icons. It uses W3 Total Cache for performance optimization and is hosted on a provider associated with csidesignpro.com. The site is mobile responsive with good SEO practices including meta tags and structured navigation. No analytics or tracking scripts were detected, indicating minimal user tracking. The technical implementation is solid but could benefit from modern security header adoption and enhanced accessibility compliance.
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 firsttexasbank.net. 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 firsttexasbank.net.

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.