linz.city

We performed a comprehensive analysis of linz.city on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 1305ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 336 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 sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-09-28, which is 89 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. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, linz.city receives an overall trust score of 71/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, linz.city receives a trust score of 71/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 89 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a quarantine policy. 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 linz.city 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 automated technology detection scan was unable to identify specific technologies on linz.city. 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.

linz.city delivers its homepage in 1305ms (server response time), which is considered somewhat slow by industry standards. The total page weight is 336 KB, and we detected 644 resource requests loading assets from 9 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 5 CSS files and 0 out of 1 JavaScript files are minified. Minifying the remaining 6 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 linz.city produces approximately 0.16g of CO₂, earning a carbon rating of B. 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 336 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for linz.city. 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.

linz.city resolves to the IPv4 address 37.252.190.194, 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: ns1.ipax.at and ns3.ipax.at. 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 linz.city is handled by qup.at with 1 MX records configured: mx.qup.at. 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 linz.city. 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 linz.city contains 1,294 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 0 H2 headings, 0 H3 headings, 0 H4 headings, 1 H5, and 1 H6 headings. The page includes 115 images. 115 images (100%) 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 0% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 202 internal links pointing to other pages on the same domain and 83 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 1 external JavaScript files, 5 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior), Progressive Web App (PWA) manifest (enabling app-like installation), and RSS feed for content syndication. 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 1 platforms: Github (@LemmyNet). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for linz.city is too long at 100 characters: "Linz Lemmy - Ein Platz für alle die in oder um Linz wohnen oder ein generelles I...". At 100 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. No meta description is configured for linz.city. 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. The canonical url is correctly set to https://linz.city/, preventing duplicate content issues, the page language is declared as en, and a favicon is configured. Open Graph meta tags are configured with 2/4 recommended fields: OG title ("Linz Lemmy - Ein Platz für alle die in oder um Linz wohnen o..."), OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol.