cityyear.org

We performed a comprehensive analysis of cityyear.org on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 4913ms. The page is served over HTTP/2 protocol with Brotli compression enabled, achieving approximately 44.7% size reduction. The total page weight is 22 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 Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-07-22, which is 22 days from now. The security headers analysis reveals a score of 80/100 (good). The following security headers are properly configured: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing Strict-Transport-Security (HSTS), which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, cityyear.org receives an overall trust score of 74/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, cityyear.org receives a trust score of 74/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 Let's Encrypt with 22 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and a well-established domain registered for over 28.1 years, indicating long-term commitment and legitimacy. Areas of concern include: 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 cityyear.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 Network Solutions, LLC based in US, with a registration date of 1998-05-31 and expiration date of 2029-05-30.

Our automated technology detection scan was unable to identify specific technologies on cityyear.org. This could indicate that the site uses server-side rendering without client-side technology fingerprints, employs aggressive code obfuscation, or uses custom-built solutions that don't match known technology signatures.

cityyear.org delivers its homepage in 4913ms (server response time), which is considered slow by industry standards. The total page weight is 22 KB, and we detected 0 resource requests loading assets from 0 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 Brotli compression for text-based assets, achieving an estimated 44.7% reduction in transfer size. Brotli is the most efficient compression algorithm available for web content, typically achieving 15-25% better compression ratios than Gzip. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. 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 cityyear.org produces approximately 0.01g 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 22 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for cityyear.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.

cityyear.org resolves to the IPv4 address 192.124.249.117, 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: ns55.worldnic.com and ns56.worldnic.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 cityyear.org is handled by Microsoft 365 with 1 MX records configured: cityyear-org.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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 cityyear.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 Network Solutions, LLC (US). It was first registered on 1998-05-31 and is set to expire on 2029-05-30, making it 28.1 years old. Our subdomain enumeration scan discovered 10 active subdomains for cityyear.org: admin.cityyear.org, api.cityyear.org, app.cityyear.org, blog.cityyear.org, cdn.cityyear.org, dev.cityyear.org, m.cityyear.org, and mail.cityyear.org. Plus 2 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of cityyear.org contains 792 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The link structure consists of 0 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 0 external JavaScript files, 0 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior). Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

No meta description is configured for cityyear.org. 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. No Open Graph tags are configured. When someone shares a link to cityyear.org 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.