verymary.berlin

We performed a comprehensive analysis of verymary.berlin on 2026-07-05. The website returned an HTTP 200 status code with a server response time of 28646ms. 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 338 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-04, which is 30 days from now. 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. Our technology detection scan identified 9 technologies across 8 categories powering verymary.berlin. The detected stack includes WordPress 6.9.4, WooCommerce, Webpack, Google Analytics 4, Microsoft Clarity, reCAPTCHA v3, Google Fonts, jQuery, and Font Awesome. The primary e-commerce platform is WooCommerce. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, verymary.berlin receives an overall trust score of 64/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, verymary.berlin receives a trust score of 64/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 30 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a none 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, 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 verymary.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 verymary.berlin and identified 9 distinct technologies across 8 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: WordPress (version 6.9.4) — manages the content and page structure for verymary.berlin. Ecommerce: WooCommerce — powers the online store and shopping functionality for verymary.berlin. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for verymary.berlin. Analytics: Google Analytics 4 and Microsoft Clarity — tracks visitor behavior and provides traffic insights for verymary.berlin. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for verymary.berlin. Fonts: Google Fonts — delivers web fonts for typography for verymary.berlin. JavaScript Library: jQuery — provides utility functions and DOM manipulation for verymary.berlin. Icon Set: Font Awesome — provides additional functionality for verymary.berlin.

verymary.berlin delivers its homepage in 28646ms (server response time), which is considered slow by industry standards. The total page weight is 338 KB, and we detected 110 resource requests loading assets from 12 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 verymary.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: 16 out of 22 CSS files and 14 out of 17 JavaScript files are minified. Minifying the remaining 9 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 verymary.berlin produces approximately 0.17g 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 338 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for verymary.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.

verymary.berlin resolves to the IPv4 address 213.133.104.78 and also supports IPv6 (2a01:4f8:d0a:2784::2), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 3 name servers: ns.second-ns.com, ns1.your-server.de, and ns3.second-ns.de. Having 3 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 verymary.berlin is handled by your-server.de with 1 MX records configured: www78.your-server.de. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 verymary.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 verymary.berlin contains 1,329 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 18 H2 headings, 7 H3 headings, 0 H4 headings. The page includes 12 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 35 internal links pointing to other pages on the same domain and 5 external links pointing to third-party websites. There are 17 external JavaScript files, 22 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), robots.txt (controls search engine crawling behavior), Schema.org structured data (AggregateRating, Answer, BreadcrumbList, City, Country, EntryPoint, FAQPage, ImageObject, ListItem, LocalBusiness, Offer, Organization, Person, PostalAddress, PriceSpecification, ProfessionalService, PropertyValueSpecification, Question, ReadAction, SearchAction, Service, WebPage, and WebSite), and RSS feed for content syndication.

The title tag for verymary.berlin is too long at 87 characters: "Professionelles Webdesign Berlin - Freelancer für Website Erstellung & Webdesign...". At 87 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. The meta description is 143 characters (well-optimized): "Elementor Freelancer aus Berlin: Ich erstelle schnelle, klare WordPress-Websites mit Elementor – für mehr Sichtbarkeit &...". 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://verymary.berlin/, preventing duplicate content issues, the page language is declared as de, the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Professionelles Webdesign Berlin - Freelancer für Website Er..."), OG description, OG image (social sharing thumbnail), 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. 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. The site implements Schema.org structured data with the following types: AggregateRating, Answer, BreadcrumbList, City, Country, EntryPoint, FAQPage, ImageObject, ListItem, LocalBusiness, Offer, Organization, Person, PostalAddress, PriceSpecification, ProfessionalService, PropertyValueSpecification, Question, ReadAction, SearchAction, Service, WebPage, and WebSite. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.