pregabalin.site

We performed a comprehensive analysis of pregabalin.site on 2026-07-04. The website returned an HTTP 200 status code with a server response time of 16073ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 951 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Sectigo Limited (OV 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 2027-03-10, which is 249 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 10 technologies across 8 categories powering pregabalin.site. The detected stack includes Vite, Google Analytics 4, Google Tag Manager, Meta Pixel, Google Ads, Twitter Pixel, VWO, New Relic, Cloudflare, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, pregabalin.site receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, pregabalin.site 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 Sectigo Limited with 249 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 pregabalin.site 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 pregabalin.site and identified 10 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. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for pregabalin.site. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for pregabalin.site. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for pregabalin.site. Advertising: Meta Pixel, Google Ads, and Twitter Pixel — handles advertising pixel tracking and conversion measurement for pregabalin.site. A/B Testing: VWO — enables experimentation and conversion optimization for pregabalin.site. Monitoring: New Relic — monitors application performance and errors for pregabalin.site. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for pregabalin.site. JavaScript Library: jQuery — provides utility functions and DOM manipulation for pregabalin.site. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-G3ZP2F3MW9, Google Tag Manager container GTM-TKQZL95, and Meta (Facebook) Pixel ID 1060020737679640. These IDs can be used to identify other websites operated by the same organization.

pregabalin.site delivers its homepage in 16073ms (server response time), which is considered slow by industry standards. The total page weight is 951 KB, and we detected 149 resource requests loading assets from 58 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 5 out of 39 JavaScript files are minified. Minifying the remaining 39 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 pregabalin.site produces approximately 0.46g of CO₂, earning a carbon rating of D. The website's carbon footprint could be reduced by optimizing images, enabling compression, reducing third-party scripts, and leveraging caching. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 951 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for pregabalin.site. 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.

pregabalin.site resolves to the IPv4 address 66.29.137.49, 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: dns1.namecheaphosting.com and dns2.namecheaphosting.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 pregabalin.site is handled by jellyfish.systems with 3 MX records configured: mx1-hosting.jellyfish.systems, mx2-hosting.jellyfish.systems, and mx3-hosting.jellyfish.systems. 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 pregabalin.site. 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 pregabalin.site contains 379 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 13 images. 5 images (38%) 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 62% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 8 internal links pointing to other pages on the same domain and 11 external links pointing to third-party websites. There are 39 external JavaScript files, 5 CSS stylesheets, and 6 iframes on the page. The site implements the following web standards and features: Schema.org structured data (AggregateOffer, Brand, BreadcrumbList, ListItem, Organization, PostalAddress, Product, and Store), Progressive Web App (PWA) manifest (enabling app-like installation), and AMP (Accelerated Mobile Pages) version. Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 1 platforms: 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 pregabalin.site is too long at 72 characters: "Setiap Detik Bermain di JODOH88 Selalu Bawa Keberuntungan dan Kesenangan". At 72 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 150 characters (well-optimized): "Nggak ada yang ngalahin serunya main di JODOH88! Dari spin pertama aja udah kerasa gacornya, hadiah sering turun, dan bi...". 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://pregabalin.site/, preventing duplicate content issues, the page language is declared as id-id, 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 ("Setiap Detik Bermain di JODOH88 Selalu Bawa Keberuntungan da..."), 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" 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: AggregateOffer, Brand, BreadcrumbList, ListItem, Organization, PostalAddress, Product, and Store. 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. The meta keywords tag contains 1 terms including JODOH88. 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.