baltimorecityfoundation.org

We performed a comprehensive analysis of baltimorecityfoundation.org on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 46522ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 772 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-08-02, which is 35 days from now. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, 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 4 technologies across 4 categories powering baltimorecityfoundation.org. The detected stack includes WordPress 6.2.8, Angular, React, and Vite. The site uses Angular as its primary framework. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, baltimorecityfoundation.org receives an overall trust score of 60/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, baltimorecityfoundation.org receives a trust score of 60/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, a valid SSL certificate issued by Google Trust Services with 35 days until expiration, and a well-established domain registered for over 15.3 years, indicating long-term commitment and legitimacy. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 baltimorecityfoundation.org 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. The domain is registered through NameCheap, Inc. based in CA, with a registration date of 2011-03-17 and expiration date of 2027-03-17.

Our technology detection engine scanned baltimorecityfoundation.org and identified 4 distinct technologies across 4 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: WordPress (version 6.2.8) — manages the content and page structure for baltimorecityfoundation.org. Framework: Angular — provides the application framework and routing for baltimorecityfoundation.org. UI Library: React — handles the user interface rendering and component management for baltimorecityfoundation.org. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for baltimorecityfoundation.org.

baltimorecityfoundation.org delivers its homepage in 46522ms (server response time), which is considered slow by industry standards. The total page weight is 772 KB, and we detected 760 resource requests loading assets from 70 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: 0 out of 0 CSS files and 0 out of 2 JavaScript files are minified. Minifying the remaining 2 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 baltimorecityfoundation.org produces approximately 0.38g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 772 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for baltimorecityfoundation.org. 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.

baltimorecityfoundation.org resolves to the IPv4 address 172.67.200.113 and also supports IPv6 (2606:4700:3033::6815:4a4a), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: dell.ns.cloudflare.com and jeff.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 baltimorecityfoundation.org is handled by Google Workspace with 1 MX records configured: ghs.google.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. 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 baltimorecityfoundation.org. 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. The domain is registered through NameCheap, Inc. (CA). It was first registered on 2011-03-17 and is set to expire on 2027-03-17, making it 15.3 years old. Our subdomain enumeration scan discovered 1 active subdomains for baltimorecityfoundation.org: www.baltimorecityfoundation.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of baltimorecityfoundation.org contains 90,793 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 153 H2 headings, 223 H3 headings, 6 H4 headings. The page includes 12 images. 6 images (50%) 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 50% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 659 internal links pointing to other pages on the same domain and 68 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 2 external JavaScript files, 0 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Schema.org structured data (BreadcrumbList, CollectionPage, EntryPoint, ListItem, SearchAction, and WebSite) and RSS feed for content syndication. Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on baltimorecityfoundation.org: Visa and Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for baltimorecityfoundation.org is well-optimized at 57 characters: "Baltimorecityfoundation.org - Baltimorecityfoundation.org". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 27 characters (acceptable): "Baltimorecityfoundation.org". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The canonical url is correctly set to https://baltimorecityfoundation.org/, preventing duplicate content issues, the page language is declared as en-us, the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Baltimorecityfoundation.org..."), OG description, OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The site implements Schema.org structured data with the following types: BreadcrumbList, CollectionPage, EntryPoint, ListItem, SearchAction, and WebSite. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.