seattle.gov

We performed a comprehensive analysis of seattle.gov on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 29956ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 43 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 Amazon (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 4 domain(s) (Subject Alternative Names) and expires on 2027-03-01, which is 245 days from now. The security headers analysis reveals a score of 65/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Content-Security-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 3 technologies across 3 categories powering seattle.gov. The detected stack includes Google Tag Manager, Google Fonts, and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, seattle.gov receives an overall trust score of 80/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, seattle.gov receives a trust score of 80/100, which places it in the "Very 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, a valid SSL certificate issued by Amazon with 245 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a quarantine policy. 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 seattle.gov 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.

Our technology detection engine scanned seattle.gov and identified 3 distinct technologies across 3 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 seattle.gov. Fonts: Google Fonts — delivers web fonts for typography for seattle.gov. Icon Set: Font Awesome — provides additional functionality for seattle.gov. We also extracted the following tracking identifiers: Google Tag Manager container GTM-PXQBQ2. These IDs can be used to identify other websites operated by the same organization.

seattle.gov delivers its homepage in 29956ms (server response time), which is considered slow by industry standards. The total page weight is 43 KB, and we detected 114 resource requests loading assets from 14 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 3 CSS files and 6 out of 10 JavaScript files are minified. Minifying the remaining 7 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 seattle.gov 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 43 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for seattle.gov. 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.

seattle.gov resolves to the IPv4 address 13.226.244.89, 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 4 A record(s) configured. The domain name system is managed by 6 name servers: ns50.ultradns2.com, ns50.ultradns2.org, pdns100.ultradns.biz, pdns100.ultradns.com, pdns100.ultradns.net, and pdns100.ultradns.org. Having 6 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 seattle.gov is handled by fireeyegov.com with 1 MX records configured: mx.us.etp.fireeyegov.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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 seattle.gov. 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 homepage of seattle.gov contains 660 words of visible text content. This is a moderate amount of content. The page is structured with 10 H2 headings, 35 H3 headings, 0 H4 headings. The page includes 13 images. 9 images (69%) 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 31% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 50 internal links pointing to other pages on the same domain and 29 external links pointing to third-party websites. There are 10 external JavaScript files, 3 CSS stylesheets, and 1 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. We detected the following payment methods accepted on seattle.gov: Discover. 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 3 platforms: Facebook (@cityofseattlegov), Twitter (@CityOfSeattle), and Instagram (@CityOfSeattleGov). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for seattle.gov is good at 16 characters: "Seattle.gov Home". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 117 characters (well-optimized): "Official city government site. Citizen, business, and visitor information sections, plus city government information.". 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.seattle.gov/, 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 seattle.gov 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.