edmonton.ca

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, edmonton.ca receives a trust score of 75/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 none policy, 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, 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 edmonton.ca 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.

🤖 AI Summary

Our technology detection engine scanned edmonton.ca and identified 8 distinct technologies across 7 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 and Drupal — manages the content and page structure for edmonton.ca. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for edmonton.ca. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for edmonton.ca. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for edmonton.ca. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for edmonton.ca. JavaScript Library: jQuery — provides utility functions and DOM manipulation for edmonton.ca. Icon Set: Font Awesome — provides additional functionality for edmonton.ca. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-DGDE39N1Z6 and Google Tag Manager container GTM-WKXCFX5. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

edmonton.ca delivers its homepage in 37152ms (server response time), which is considered slow by industry standards. The total page weight is 63 KB, and we detected 130 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: 2 out of 5 CSS files and 11 out of 22 JavaScript files are minified. Minifying the remaining 14 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 edmonton.ca 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 63 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for edmonton.ca. 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.

🤖 AI Summary

edmonton.ca resolves to the IPv4 address 35.190.75.248, 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 4 name servers: champ.gov.edmonton.ab.ca, dns2.gov.edmonton.ab.ca, ns1.d-zone.ca, and ns2.d-zone.ca. Having 4 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 edmonton.ca is handled by fireeyecloud.com with 4 MX records configured: alt1.us.email.fireeyecloud.com, primary.us.email.fireeyecloud.com, and alt2.us.email.fireeyecloud.com and 1 more. 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 (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 edmonton.ca. 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 3 active subdomains for edmonton.ca: ftp.edmonton.ca, portal.edmonton.ca, and www.edmonton.ca. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of edmonton.ca contains 359 words of visible text content. This is a moderate amount of content. The page is structured with 11 H2 headings, 20 H3 headings, 0 H4 headings, 2 H5, and 0 H6 headings. The page includes 8 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 75 internal links pointing to other pages on the same domain and 13 external links pointing to third-party websites. There are 22 external JavaScript files, 5 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. The website has social media presence across 4 platforms: Facebook (@cityofedmonton), Twitter (@cityofedmonton), Instagram (@cityofedmonton), and Linkedin (@city-of-edmonton). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for edmonton.ca is good at 23 characters: "Home | City of Edmonton". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 133 characters (well-optimized): "Official site of the City of Edmonton in Alberta, Canada. Learn about City services, programs, attractions, events and C...". 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://www.edmonton.ca/, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to edmonton.ca 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.

🤖 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 edmonton.ca. 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: ga4_id: G-DGDE39N1Z6, gtm_id: GTM-WKXCFX5.