bore.pub

We performed a comprehensive analysis of bore.pub on 2026-07-08. The website returned an HTTP 200 status code with a server response time of 16272ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 315 KB. Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 85/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing 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 2 technologies across 2 categories powering bore.pub. The detected stack includes React and Vite. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, bore.pub receives an overall trust score of 67/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, bore.pub receives a trust score of 67/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 and HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks. Areas of concern include: 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 bore.pub 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 bore.pub and identified 2 distinct technologies across 2 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. UI Library: React — handles the user interface rendering and component management for bore.pub. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for bore.pub.

bore.pub delivers its homepage in 16272ms (server response time), which is considered slow by industry standards. The total page weight is 315 KB, and we detected 329 resource requests loading assets from 24 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 39 CSS files and 0 out of 91 JavaScript files are minified. Minifying the remaining 130 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 bore.pub produces approximately 0.15g 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 315 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for bore.pub. 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.

bore.pub resolves to the IPv4 address 159.223.110.159 and also supports IPv6 (2604:a880:400:d1:0:4:822c:e001), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 3 name servers: ns1.digitalocean.com, ns2.digitalocean.com, and ns3.digitalocean.com. 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. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. DMARC is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. 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 bore.pub. 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 bore.pub contains 1,646 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 17 H2 headings, 19 H3 headings, 2 H4 headings. The page includes 3 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 155 internal links pointing to other pages on the same domain and 26 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 91 external JavaScript files, 39 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on bore.pub: Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 2 platforms: Twitter (@ekzhang1\) and Github (@cmc_internal). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for bore.pub is too long at 91 characters: "GitHub - ekzhang/bore: 🕳 bore is a simple CLI tool for making tunnels to localho...". At 91 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 74 characters (well-optimized): "🕳 bore is a simple CLI tool for making tunnels to localhost - ekzhang/bore". 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 page language is declared as en and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("GitHub - ekzhang/bore: 🕳 bore is a simple CLI tool for makin..."), OG description, OG image (social sharing thumbnail), OG type (object). 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.