amarillo.gov Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of amarillo.gov on 2026-06-27. The website returned an HTTP 403 status code with a server response time of 9332ms. The page is served over HTTP/2 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 1 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 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.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, amarillo.gov receives an overall trust score of 63/100, classified as "Likely Safe".
HTTP Response
Status403
Response Time9332ms
ProtocolHTTP/2
Page Size1 KB
CompressionNone
Compression SavingsN/A
CDNNo
Server—
Total Requests0
3rd Party Domains0
RedirectNone
Detected Technologies (0)
Security Headers
✗
Content-Security-Policy
Not set
✗
Strict-Transport-Security (HSTS)
Not set
✗
X-Frame-Options
Not set
✗
X-Content-Type-Options
Not set
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerGoDaddy.com, Inc.
Issuer FullcountryName=US, stateOrProvinceName=Arizona, localityName=Scottsdale, organizationName=GoDaddy.com, Inc., organizationalUnitName=http://certs.godaddy.com/repository/, commonName=Go Daddy Secure Certificate Authority - G2
SubjectcountryName=US, stateOrProvinceName=Texas, localityName=Amarillo, organizationName=City of Amarillo, commonName=*.amarillo.gov
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
amarillo.gov Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, amarillo.gov receives a trust score of 63/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, 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, 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 amarillo.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.
Trust Signals
✅ Valid HTTPS
✅ SPF configured
✅ DMARC configured (p=reject)
✅ DKIM configured
⚠️ DNSSEC not enabled
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ 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
amarillo.gov Technology Stack & Detected Technologies
🤖 AI Summary
Our automated technology detection scan was unable to identify specific technologies on amarillo.gov. 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.
amarillo.gov Performance, Speed & Core Web Vitals
🤖 AI Summary
amarillo.gov delivers its homepage in 9332ms (server response time), which is considered slow by industry standards. The total page weight is 1 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.
No compression is currently enabled on amarillo.gov. 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.
From an environmental perspective, each page view of amarillo.gov produces approximately 0.0g 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 1 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for amarillo.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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.0g
RatingA
Page Weight & Optimization
HTML Size1 KB
CompressionNone
Compression SavingsN/A
CDNNo
Total Requests0
3rd Party Domains0
CSS Minified0/0
JS Minified0/0
amarillo.gov DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
amarillo.gov resolves to the IPv4 address 150.171.109.198 and also supports IPv6 (2603:1061:14:c5::1), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured.
The domain name system is managed by 2 name servers: roan.ns.cloudflare.com and violet.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 amarillo.gov is handled by mimecast.com with 2 MX records configured: us-smtp-inbound-1.mimecast.com and us-smtp-inbound-2.mimecast.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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. 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 amarillo.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.
Our subdomain enumeration scan discovered 7 active subdomains for amarillo.gov: ftp.amarillo.gov, m.amarillo.gov, mail.amarillo.gov, staging.amarillo.gov, support.amarillo.gov, webmail.amarillo.gov, and www.amarillo.gov. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
roan.ns.cloudflare.com
violet.ns.cloudflare.com
MX
us-smtp-inbound-1.mimecast.com
us-smtp-inbound-2.mimecast.com
Email & Authentication
MX Providermimecast.com
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportYes ✓
Subdomains (7 found)
ftp.amarillo.gov m.amarillo.gov mail.amarillo.gov staging.amarillo.gov support.amarillo.gov webmail.amarillo.gov www.amarillo.gov
amarillo.gov Page Content, Images & Accessibility
🤖 AI Summary
The homepage of amarillo.gov contains 7 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 1 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.
Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
Content Structure
H1—
H2 Tags1
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links0
External Links0
Assets & Features
JavaScript Files0
JS Minified0/0
CSS Files0
CSS Minified0/0
Iframes0
Images0
Missing Alt0
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
amarillo.gov SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for amarillo.gov is good at 19 characters: "Service unavailable". The length is acceptable, though it may be slightly truncated in some search result displays.
No meta description is configured for amarillo.gov. 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 amarillo.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.
Google SERP Preview
Service unavailable
https://amarillo.gov
Meta Tags
TitleService unavailable...
Title Length19 chars
Meta Desc Length0 chars
H1—
Language—
Canonical—
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Type—
OG ImageNot set
Twitter Card—
FaviconNot set