planetarium.berlin

We performed a comprehensive analysis of planetarium.berlin on 2026-07-07. The website returned an HTTP 200 status code with a server response time of 10743ms. 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 155 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 2 domain(s) (Subject Alternative Names) and expires on 2026-08-17, which is 41 days from now. The security headers analysis reveals a score of 30/100 (below average). The following security headers are properly configured: X-Frame-Options and X-Content-Type-Options. However, the site is missing Content-Security-Policy, 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 6 technologies across 6 categories powering planetarium.berlin. The detected stack includes Drupal, Bootstrap, Matomo, Meta Pixel, YouTube Embed, and jQuery 3.6.4.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, planetarium.berlin receives an overall trust score of 71/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, planetarium.berlin 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 41 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, 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 planetarium.berlin 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 planetarium.berlin and identified 6 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: Drupal — manages the content and page structure for planetarium.berlin. CSS Framework: Bootstrap — provides the styling and responsive layout system for planetarium.berlin. Analytics: Matomo — tracks visitor behavior and provides traffic insights for planetarium.berlin. Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for planetarium.berlin. Video: YouTube Embed — provides video hosting and playback for planetarium.berlin. JavaScript Library: jQuery (version 3.6.4.) — provides utility functions and DOM manipulation for planetarium.berlin. We also extracted the following tracking identifiers: Meta (Facebook) Pixel ID 536118007732277. These IDs can be used to identify other websites operated by the same organization.

planetarium.berlin delivers its homepage in 10743ms (server response time), which is considered slow by industry standards. The total page weight is 155 KB, and we detected 229 resource requests loading assets from 6 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 planetarium.berlin. 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. Asset minification status: 0 out of 2 CSS files and 5 out of 16 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 planetarium.berlin 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 155 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for planetarium.berlin. 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.

planetarium.berlin resolves to the IPv4 address 78.47.33.218 and also supports IPv6 (2a01:4f8:c0c:1511::2), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 2 name servers: ns59.domaincontrol.com and ns60.domaincontrol.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 planetarium.berlin is handled by planetarium.berlin with 1 MX records configured: mx01.planetarium.berlin. 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 planetarium.berlin. 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 planetarium.berlin contains 600 words of visible text content. This is a moderate amount of content. The page is structured with 30 H2 headings, 15 H3 headings, 0 H4 headings. The page includes 36 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 109 internal links pointing to other pages on the same domain and 24 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 16 external JavaScript files, 2 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. The website has social media presence across 3 platforms: Facebook (@zeiss.grossplanetarium), Instagram (@planetarium.berlin), and Tiktok (@planetarium.berlin). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for planetarium.berlin is good at 27 characters: "Stiftung Planetarium Berlin". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 205 characters (slightly long): "Die Stiftung Planetarium Berlin wurde zum 1. Juli 2016 als rechtsfähige Stiftung des öffentlichen Rechts errichtet und v...". 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.planetarium.berlin/, preventing duplicate content issues, the page language is declared as de, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to planetarium.berlin 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.