vibey.cfd

We performed a comprehensive analysis of vibey.cfd on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 17501ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 50 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 9 domain(s) (Subject Alternative Names) and expires on 2026-08-27, which is 58 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 3 technologies across 3 categories powering vibey.cfd. The detected stack includes Tailwind CSS, Cloudflare, and Google Fonts. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, vibey.cfd receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, vibey.cfd 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 58 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 vibey.cfd 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 vibey.cfd 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. CSS Framework: Tailwind CSS — provides the styling and responsive layout system for vibey.cfd. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for vibey.cfd. Fonts: Google Fonts — delivers web fonts for typography for vibey.cfd.

vibey.cfd delivers its homepage in 17501ms (server response time), which is considered slow by industry standards. The total page weight is 50 KB, and we detected 17 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 2 CSS files and 1 out of 4 JavaScript files are minified. Minifying the remaining 5 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 vibey.cfd produces approximately 0.02g 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 50 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for vibey.cfd. 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.

vibey.cfd resolves to the IPv4 address 202.10.43.18 and also supports IPv6 (2001:df0:27b:3::a042), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 4 name servers: ns1.rumahweb.com, ns2.rumahweb.com, ns3.rumahweb.net, and ns4.rumahweb.net. 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 vibey.cfd is handled by vibey.cfd with 1 MX records configured: vibey.cfd. 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 vibey.cfd. 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 vibey.cfd contains 292 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 2 H2 headings, 5 H3 headings, 1 H4 headings. The page includes 2 images. 1 images (50%) 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 50% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 4 internal links pointing to other pages on the same domain and 2 external links pointing to third-party websites. There are 4 external JavaScript files, 2 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) 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 title tag for vibey.cfd is good at 67 characters: "Dakila Shortlink — Enterprise-Grade URL Shortener & Link Management". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 194 characters (slightly long): "Optimized for speed and security, Dakila Shortlink routes your audience directly to destination URLs. Get zero-redirect ...". 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://laju.asia, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to index, follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Dakila Shortlink — Enterprise-Grade URL Shortener & Link Man..."), 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 8 terms including dakila shortlink, url shortener, link management, direct url redirect, and custom alias shortlink. 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.