356bank.com

HTTPS HTTP/2 HSTS Gzip Crawled in 34,449ms · June 27, 2026 15:02 UTC

356bank.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of 356bank.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 18542ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 49 KB, and the site is served behind a CDN (Content Delivery Network). Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 50/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 1 technologies across 1 categories powering 356bank.com. The detected stack includes Google Analytics 4. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 356bank.com receives an overall trust score of 72/100, classified as "Likely Safe".
72
/ 100
Trust Score
50
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time18542ms
ProtocolHTTP/2
Page Size49 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests109
3rd Party Domains12
Redirect1 hop(s)
Detected Technologies (1)
📊 Google Analytics 4
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Set ✓
X-Frame-Options
Set ✓
X-Content-Type-Options
Set ✓
Referrer-Policy
Not set
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=E8
SubjectcommonName=356bank.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

356bank.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, 356bank.com receives a trust score of 72/100, which places it in the "Likely Safe" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, missing Referrer-Policy, potentially leaking URL information to third parties, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked 356bank.com against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.
72
/ 100
Likely Safe
Trust Signals
Valid HTTPS
HSTS enabled
SPF configured
DMARC configured (p=reject)
DKIM configured
⚠️ DNSSEC not enabled
Sitemap.xml found
⚠️ Missing Content-Security-Policy
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
Google Safe Browsing clean
Phishtank clean
Urlhaus clean
Openphish clean
Dnsfilter clean
Spamhaus Dbl clean
Surbl clean
Virustotal clean

356bank.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned 356bank.com and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for 356bank.com. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-JX74XB3HLB. These IDs can be used to identify other websites operated by the same organization.
Analytics
📊 Google Analytics 4(95%)
Tracking IDs
ga4_idG-JX74XB3HLB

356bank.com Performance, Speed & Core Web Vitals

🤖 AI Summary
356bank.com delivers its homepage in 18542ms (server response time), which is considered slow by industry standards. The total page weight is 49 KB, and we detected 109 resource requests loading assets from 12 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. Asset minification status: 1 out of 1 CSS files and 2 out of 5 JavaScript files are minified. Minifying the remaining 3 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of 356bank.com produces approximately 0.02g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 49 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 356bank.com. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.02g
RatingA
Page Weight & Optimization
HTML Size49 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests109
3rd Party Domains12
CSS Minified1/1
JS Minified2/5

356bank.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
356bank.com resolves to the IPv4 address 104.18.24.218, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 2 A record(s) configured. The domain name system is managed by 3 name servers: ns1.boitdns.com, ns2.boitdns.com, and ns3.boitdns.com. Having 3 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for 356bank.com is handled by arsmtp.com with 2 MX records configured: 356bank.com.1.0001.arsmtp.com and 356bank.com.2.0001.arsmtp.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. DMARC (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is not enabled for 356bank.com. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions. Our subdomain enumeration scan discovered 25 active subdomains for 356bank.com: admin.356bank.com, api.356bank.com, app.356bank.com, apps.356bank.com, blog.356bank.com, cdn.356bank.com, community.356bank.com, and dev.356bank.com. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
104.18.24.218
104.18.25.218
NS
ns1.boitdns.com
ns2.boitdns.com
ns3.boitdns.com
MX
356bank.com.1.0001.arsmtp.com
356bank.com.2.0001.arsmtp.com
Email & Authentication
SPF
DMARC p=reject
DKIM
DNSSEC
MX Providerarsmtp.com
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportNo
Subdomains (25 found)
admin.356bank.com api.356bank.com app.356bank.com apps.356bank.com blog.356bank.com cdn.356bank.com community.356bank.com dev.356bank.com developers.356bank.com docs.356bank.com ftp.356bank.com help.356bank.com m.356bank.com mail.356bank.com partners.356bank.com portal.356bank.com shop.356bank.com smtp.356bank.com staging.356bank.com static.356bank.com status.356bank.com store.356bank.com support.356bank.com webmail.356bank.com www.356bank.com

356bank.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of 356bank.com contains 661 words of visible text content. This is a moderate amount of content. The page is structured with 8 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 25 images. 5 images (20%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 80% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 52 internal links pointing to other pages on the same domain and 12 external links pointing to third-party websites. There are 5 external JavaScript files, 1 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages). Notable missing features: robots.txt and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 3 platforms: Facebook (@ffsbofcu), Twitter (@FFSBOFCU), and Linkedin (@ffsbcu). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
661
Words
25
Images
80%
Alt Text Score
49
Page Size (KB)
Content Structure
H1First Federal Savings Bank of Champaign-Urbana
H2 Tags8
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links52
External Links12
Assets & Features
JavaScript Files5
JS Minified2/5
CSS Files1
CSS Minified1/1
Iframes0
Images25
Missing Alt5
SitemapYes ✓
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Social Media Presence
Facebook: @ffsbofcuTwitter: @FFSBOFCULinkedin: @ffsbcu

356bank.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for 356bank.com is good at 69 characters: "Home | First Federal Savings Bank of Champaign-Urbana | Champaign, IL". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for 356bank.com. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The page language is declared as en. No Open Graph tags are configured. When someone shares a link to 356bank.com on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing.
Google SERP Preview
Home | First Federal Savings Bank of Champaign-Urbana | Champaign, IL
https://356bank.com
Meta Tags
TitleHome | First Federal Savings Bank of Champaign-Urbana | Cham...
Title Length69 chars
Meta Desc Length0 chars
H1First Federal Savings Bank of Champaign-Urbana
Languageen
Canonical
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconNot set