railway.uz

We performed a comprehensive analysis of railway.uz on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 2964ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 174 KB. 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 ECDSA-SHA384 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-06-30, which is 0 days from now. The security headers analysis reveals a score of 50/100 (moderate). The following security headers are properly configured: Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options. However, the site is missing Strict-Transport-Security (HSTS), 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 3 technologies across 3 categories powering railway.uz. The detected stack includes Vite, reCAPTCHA v3, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, railway.uz receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, railway.uz receives a trust score of 66/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 0 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and a well-established domain registered for over 10.3 years, indicating long-term commitment and legitimacy. Areas of concern include: 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 railway.uz 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 Denishev Sultan based in UZ, with a registration date of 2016-03-01 and expiration date of 2027-03-01.

Our technology detection engine scanned railway.uz 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. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for railway.uz. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for railway.uz. JavaScript Library: jQuery — provides utility functions and DOM manipulation for railway.uz.

railway.uz delivers its homepage in 2964ms (server response time), which is considered slow by industry standards. The total page weight is 174 KB, and we detected 440 resource requests loading assets from 45 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: 3 out of 8 CSS files and 5 out of 13 JavaScript files are minified. Minifying the remaining 13 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 railway.uz produces approximately 0.08g 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 174 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for railway.uz. 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.

railway.uz resolves to the IPv4 address 109.207.255.226, 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 2 A record(s) configured. The domain name system is managed by 1 name servers: ns.railway.uz. Having only one name server creates a single point of failure. The choice of name servers often indicates the DNS hosting provider or CDN service being used. Email for railway.uz is handled by railway.uz with 6 MX records configured: m.railway.uz, ns.railway.uz, and mail.railway.uz and 3 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 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 railway.uz. 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 Denishev Sultan (UZ). It was first registered on 2016-03-01 and is set to expire on 2027-03-01, making it 10.3 years old. Our subdomain enumeration scan discovered 2 active subdomains for railway.uz: mail.railway.uz and www.railway.uz. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of railway.uz contains 1,956 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 1 H2 headings, 12 H3 headings, 31 H4 headings, 8 H5, and 1 H6 headings. The page includes 54 images. 5 images (9%) 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 91% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 211 internal links pointing to other pages on the same domain and 55 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 13 external JavaScript files, 8 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 2 platforms: Facebook (@uzrailway) and Instagram (@uzrailways_uz). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for railway.uz is well-optimized at 60 characters: "«O‘zbekiston temir yo‘llari» АJ | O‘zbekiston temir yo‘llari". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 503 characters (slightly long): "“O’zbekiston temir yo’llari” AJ O’zbekiston respublikasi hududida joylashgan sobiq O’rta Osiyo temir yo’llari bazasida 1...". 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 page language is declared as uz and a favicon is configured. Open Graph meta tags are configured with 1/4 recommended fields: OG image (social sharing thumbnail), 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.