b2sign.com

HTTPS HTTP/1.1 HSTS Gzip Crawled in 63,147ms · June 27, 2026 15:11 UTC

b2sign.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of b2sign.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 28981ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 138 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 50/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Content-Type-Options, and Permissions-Policy. However, the site is missing Content-Security-Policy, X-Frame-Options, and Referrer-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, b2sign.com receives an overall trust score of 70/100, classified as "Likely Safe".
70
/ 100
Trust Score
50
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time28981ms
ProtocolHTTP/1.1
Page Size138 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Servernginx
Total Requests85
3rd Party Domains2
Redirect2 hop(s)
Detected Technologies (0)
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Set ✓
X-Frame-Options
Not set
X-Content-Type-Options
Set ✓
Referrer-Policy
Not set
Permissions-Policy
Set ✓
SSL Certificate
IssuerSectigo Limited
Issuer FullcountryName=GB, organizationName=Sectigo Limited, commonName=Sectigo Public Server Authentication CA DV R36
SubjectcommonName=b2sign.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

b2sign.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, b2sign.com receives a trust score of 70/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. 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 b2sign.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.
70
/ 100
Likely Safe
Trust Signals
Valid HTTPS
HSTS enabled
SPF configured
DMARC configured (p=none)
DKIM configured
⚠️ DNSSEC not enabled
Sitemap.xml found
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
Google Safe Browsing clean
Phishtank clean
Urlhaus clean
Openphish clean
Dnsfilter clean
Spamhaus Dbl clean
Surbl clean
Virustotal clean

b2sign.com Technology Stack & Detected Technologies

🤖 AI Summary
Our automated technology detection scan was unable to identify specific technologies on b2sign.com. This could indicate that the site uses server-side rendering without client-side technology fingerprints, employs aggressive code obfuscation, or uses custom-built solutions that don't match known technology signatures.

b2sign.com Performance, Speed & Core Web Vitals

🤖 AI Summary
b2sign.com delivers its homepage in 28981ms (server response time), which is considered slow by industry standards. The total page weight is 138 KB, and we detected 85 resource requests loading assets from 2 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 0 out of 1 JavaScript files are minified. Minifying the remaining 3 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 b2sign.com produces approximately 0.07g 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 138 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for b2sign.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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.07g
RatingA
Page Weight & Optimization
HTML Size138 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests85
3rd Party Domains2
CSS Minified0/2
JS Minified0/1

b2sign.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
b2sign.com resolves to the IPv4 address 13.57.182.207, 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 4 name servers: ns-1205.awsdns-22.org, ns-1651.awsdns-14.co.uk, ns-415.awsdns-51.com, and ns-887.awsdns-46.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 b2sign.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 (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is not enabled for b2sign.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. Our subdomain enumeration scan discovered 2 active subdomains for b2sign.com: admin.b2sign.com and www.b2sign.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
13.57.182.207
NS
ns-1205.awsdns-22.org
ns-1651.awsdns-14.co.uk
ns-415.awsdns-51.com
ns-887.awsdns-46.net
MX
aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
aspmx2.googlemail.com
aspmx3.googlemail.com
Email & Authentication
SPF
DMARC p=none
DKIM
DNSSEC
MX ProviderGoogle Workspace
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportNo
Subdomains (2 found)
admin.b2sign.com www.b2sign.com

b2sign.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of b2sign.com contains 332 words of visible text content. This is a moderate amount of content. The page is structured with 1 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 5 images. 4 images (80%) 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 20% 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 5 external links pointing to third-party websites. There are 1 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 Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: 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 b2sign.com: JCB. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.
332
Words
5
Images
20%
Alt Text Score
138
Page Size (KB)
Content Structure
H1
H2 Tags1
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links63
External Links5
Assets & Features
JavaScript Files1
JS Minified0/1
CSS Files2
CSS Minified0/2
Iframes0
Images5
Missing Alt4
SitemapYes ✓
Robots.txtNo
PWAYes ✓
AMPNo
RSS FeedNo
Payment Methods Detected
💳 JCB

b2sign.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for b2sign.com is well-optimized at 33 characters: "Free Same Day Turnaround Products". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. No meta description is configured for b2sign.com. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The page language is declared as en and a favicon is configured. No Open Graph tags are configured. When someone shares a link to b2sign.com on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing.
Google SERP Preview
Free Same Day Turnaround Products
https://b2sign.com
Meta Tags
TitleFree Same Day Turnaround Products...
Title Length33 chars
Meta Desc Length0 chars
H1
Languageen
Canonical
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconSet ✓