ollocdam.com

We performed a comprehensive analysis of ollocdam.com on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 22081ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 263 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_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 7 domain(s) (Subject Alternative Names) and expires on 2026-09-01, which is 62 days from now. The security headers analysis reveals a score of 50/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Content-Type-Options, and Referrer-Policy. However, the site is missing Content-Security-Policy, X-Frame-Options, 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 8 technologies across 6 categories powering ollocdam.com. The detected stack includes Next.js, Google Analytics 4, Google Tag Manager, Meta Pixel, TikTok Pixel, Twitter Pixel, Vimeo, and jQuery 3.7.1.. The site uses Next.js as its primary framework. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ollocdam.com receives an overall trust score of 75/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, ollocdam.com receives a trust score of 75/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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, a valid SSL certificate issued by Let's Encrypt with 62 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and a domain registered for 1.3 years. 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), 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 ollocdam.com 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 Gabia, Inc. based in KR, with a registration date of 2025-03-12 and expiration date of 2027-03-12.

Our technology detection engine scanned ollocdam.com and identified 8 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. Framework: Next.js — provides the application framework and routing for ollocdam.com. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for ollocdam.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for ollocdam.com. Advertising: Meta Pixel, TikTok Pixel, and Twitter Pixel — handles advertising pixel tracking and conversion measurement for ollocdam.com. Video: Vimeo — provides video hosting and playback for ollocdam.com. JavaScript Library: jQuery (version 3.7.1.) — provides utility functions and DOM manipulation for ollocdam.com. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-5GSEH8489X, Google Tag Manager container GTM-WPNGFM2J, Meta (Facebook) Pixel ID 1880925042680225, and TikTok Pixel ID D1N9BGJC77U69CK56F60. These IDs can be used to identify other websites operated by the same organization.

ollocdam.com delivers its homepage in 22081ms (server response time), which is considered slow by industry standards. The total page weight is 263 KB, and we detected 117 resource requests loading assets from 16 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 2 CSS files and 2 out of 17 JavaScript files are minified. Minifying the remaining 17 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 ollocdam.com produces approximately 0.13g 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 263 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ollocdam.com. 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.

ollocdam.com resolves to the IPv4 address 183.111.139.230, 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 4 A record(s) configured. The domain name system is managed by 4 name servers: dns1.cafe24.co.kr, dns1.cafe24.com, dns2.cafe24.co.kr, and dns2.cafe24.com. Having 4 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 ollocdam.com is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 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 (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 ollocdam.com. 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 Gabia, Inc. (KR). It was first registered on 2025-03-12 and is set to expire on 2027-03-12, making it 1.3 years old. Our subdomain enumeration scan discovered 10 active subdomains for ollocdam.com: admin.ollocdam.com, api.ollocdam.com, app.ollocdam.com, blog.ollocdam.com, cdn.ollocdam.com, dev.ollocdam.com, m.ollocdam.com, and mail.ollocdam.com. Plus 2 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of ollocdam.com contains 1,254 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, 2 H3 headings, 0 H4 headings. The page includes 16 images. 10 images (62%) 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 38% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 63 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 17 external JavaScript files, 2 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and robots.txt (controls search engine crawling behavior). Notable missing features: 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 (@tr) and Twitter (@uwt.js). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for ollocdam.com is good at 8 characters: "올록담ㅣ올리브3". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 45 characters (acceptable): "올리브 마스터가 설계한 지중해 3대 올리브, 올록담의 올리브3 를 경험해 보세요.". 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://ollocdam.com/, preventing duplicate content issues, the page language is declared as ko, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("올록담ㅣ올리브3..."), 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. The meta keywords tag contains 1 terms including 올록담. Note: Google has officially confirmed that it does not use the meta keywords tag as a ranking signal. However, some other search engines (Bing, Yandex) may still reference it.