buffalofed.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of buffalofed.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 21028ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 57 KB.
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 70/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options. However, the site is missing 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 5 technologies across 5 categories powering buffalofed.com. The detected stack includes Google Tag Manager, Meta Pixel, New Relic, Google Fonts, and jQuery.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, buffalofed.com receives an overall trust score of 70/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time21028ms
ProtocolHTTP/1.1
Page Size57 KB
CompressionNone
Compression SavingsN/A
CDNNo
Server—
Total Requests96
3rd Party Domains10
Redirect1 hop(s)
Detected Technologies (5)
🏷️ Google Tag Manager
📢 Meta Pixel
📡 New Relic
🔤 Google Fonts
📦 jQuery
Security Headers
✓
Content-Security-Policy
Set ✓
✓
Strict-Transport-Security (HSTS)
Set ✓
✓
X-Content-Type-Options
Set ✓
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerDigiCert Inc
Issuer FullcountryName=US, organizationName=DigiCert Inc, commonName=DigiCert Global G2 TLS RSA SHA256 2020 CA1
SubjectcountryName=US, stateOrProvinceName=Wyoming, localityName=Buffalo, organizationName=Buffalo Federal Bank, commonName=www.buffalofed.com
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_128_GCM_SHA256
Algorithm—
Issued—
Expires— (? days)
SANs—
buffalofed.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, buffalofed.com receives a trust score of 70/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, and SPF (Sender Policy Framework) email authentication preventing email spoofing.
Areas of concern include: 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 buffalofed.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.
Trust Signals
✅ Valid HTTPS
✅ HSTS enabled
✅ SPF configured
⚠️ DNSSEC not enabled
⚠️ 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
buffalofed.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned buffalofed.com and identified 5 distinct technologies across 5 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records.
Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for buffalofed.com.
Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for buffalofed.com.
Monitoring: New Relic — monitors application performance and errors for buffalofed.com.
Fonts: Google Fonts — delivers web fonts for typography for buffalofed.com.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for buffalofed.com.
We also extracted the following tracking identifiers: Google Tag Manager container GTM-PCNHV2X and Meta (Facebook) Pixel ID 1306733039799684. These IDs can be used to identify other websites operated by the same organization.
Tag Manager
🏷️ Google Tag Manager(95%)
Advertising
Monitoring
Fonts
JavaScript Library
Tracking IDs
gtm_idGTM-PCNHV2X
meta_pixel_id1306733039799684
buffalofed.com Performance, Speed & Core Web Vitals
🤖 AI Summary
buffalofed.com delivers its homepage in 21028ms (server response time), which is considered slow by industry standards. The total page weight is 57 KB, and we detected 96 resource requests loading assets from 10 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.
No compression is currently enabled on buffalofed.com. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available.
Asset minification status: 1 out of 4 CSS files and 2 out of 7 JavaScript files are minified. Minifying the remaining 8 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.
From an environmental perspective, each page view of buffalofed.com produces approximately 0.03g 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 57 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for buffalofed.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.03g
RatingA
Page Weight & Optimization
HTML Size57 KB
CompressionNone
Compression SavingsN/A
CDNNo
Total Requests96
3rd Party Domains10
CSS Minified1/4
JS Minified2/7
buffalofed.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
buffalofed.com resolves to the IPv4 address 199.186.59.48, 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 1 A record(s) configured.
The domain name system is managed by 2 name servers: adaline.ns.cloudflare.com and porter.ns.cloudflare.com. Having 2 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 buffalofed.com is handled by Microsoft 365 with 1 MX records configured: buffalofed-com.mail.protection.outlook.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 is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic.
DNSSEC is not enabled for buffalofed.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 buffalofed.com: admin.buffalofed.com, api.buffalofed.com, app.buffalofed.com, apps.buffalofed.com, blog.buffalofed.com, cdn.buffalofed.com, community.buffalofed.com, and dev.buffalofed.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
NS
adaline.ns.cloudflare.com
porter.ns.cloudflare.com
MX
buffalofed-com.mail.protection.outlook.com
Email & Authentication
MX ProviderMicrosoft 365
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (25 found)
admin.buffalofed.com api.buffalofed.com app.buffalofed.com apps.buffalofed.com blog.buffalofed.com cdn.buffalofed.com community.buffalofed.com dev.buffalofed.com developers.buffalofed.com docs.buffalofed.com ftp.buffalofed.com help.buffalofed.com m.buffalofed.com mail.buffalofed.com partners.buffalofed.com portal.buffalofed.com shop.buffalofed.com smtp.buffalofed.com staging.buffalofed.com static.buffalofed.com status.buffalofed.com store.buffalofed.com support.buffalofed.com webmail.buffalofed.com www.buffalofed.com
buffalofed.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of buffalofed.com contains 497 words of visible text content. This is a moderate amount of content. The page is structured with 4 H2 headings, 0 H3 headings, 0 H4 headings.
The page includes 15 images. 4 images (27%) 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 73% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 58 internal links pointing to other pages on the same domain and 9 external links pointing to third-party websites. There are 7 external JavaScript files, 4 CSS stylesheets, and 1 iframes on the page.
Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
We detected the following payment methods accepted on buffalofed.com: Mastercard. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.
The website has social media presence across 1 platforms: Facebook (@tr). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1The Banks of Buffalo Gillette Sheridan
H2 Tags4
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links58
External Links9
Assets & Features
JavaScript Files7
JS Minified2/7
CSS Files4
CSS Minified1/4
Iframes1
Images15
Missing Alt4
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Payment Methods Detected
Social Media Presence
buffalofed.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for buffalofed.com is too long at 80 characters: "The Banks of Buffalo Gillette Sheridan - Welcome to our family of Wyoming Banks!". At 80 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning.
No meta description is configured for buffalofed.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-us and a favicon is configured.
No Open Graph tags are configured. When someone shares a link to buffalofed.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
The Banks of Buffalo Gillette Sheridan - Welcome to our family of Wyoming Banks!
https://buffalofed.com
Meta Tags
TitleThe Banks of Buffalo Gillette Sheridan - Welcome to our fami...
Title Length80 chars
Meta Desc Length0 chars
H1The Banks of Buffalo Gillette Sheridan
Languageen-US
Canonical—
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Type—
OG ImageNot set
Twitter Card—
FaviconSet ✓
buffalofed.com Related Domains & Cross-References
🤖 AI Summary
Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with buffalofed.com. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: gtm_id: GTM-PCNHV2X, meta_pixel_id: 1306733039799684.
Tracking IDs for Cross-Referencing
gtm_idGTM-PCNHV2X
meta_pixel_id1306733039799684
Related Domains
Related domain data requires database (populated after batch crawl)