681busterminal.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of 681busterminal.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 23268ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 6.6% size reduction. The total page weight is 5 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 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 2 technologies across 2 categories powering 681busterminal.com. The detected stack includes Google Analytics 4 and Google AdSense.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 681busterminal.com receives an overall trust score of 59/100, classified as "Caution Advised".
HTTP Response
Status200 OK
Response Time23268ms
ProtocolHTTP/1.1
Page Size5 KB
CompressionGzip
Compression Savings~6.6%
CDNNo
ServerApache/2
Total Requests20
3rd Party Domains9
Redirect1 hop(s)
Detected Technologies (2)
📊 Google Analytics 4
📢 Google AdSense
Security Headers
✗
Content-Security-Policy
Not set
✗
Strict-Transport-Security (HSTS)
Not set
✗
X-Frame-Options
Not set
✗
X-Content-Type-Options
Not set
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=YR2
SubjectcommonName=681busterminal.com
Type—
TLS VersionTLS 1.2
Cipher SuiteECDHE-RSA-AES128-GCM-SHA256
Algorithm—
Issued—
Expires— (? days)
SANs—
681busterminal.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, 681busterminal.com receives a trust score of 59/100, which places it in the "Caution Advised" 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, 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 681busterminal.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.
Trust Signals
✅ Valid HTTPS
✅ SPF configured
✅ DMARC configured (p=none)
⚠️ DNSSEC not enabled
⚠️ 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
681busterminal.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned 681busterminal.com 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.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for 681busterminal.com.
Advertising: Google AdSense — handles advertising pixel tracking and conversion measurement for 681busterminal.com.
Analytics
📊 Google Analytics 4(95%)
Advertising
681busterminal.com Performance, Speed & Core Web Vitals
🤖 AI Summary
681busterminal.com delivers its homepage in 23268ms (server response time), which is considered slow by industry standards. The total page weight is 5 KB, and we detected 20 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 6.6% 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 0 CSS files and 0 out of 3 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 681busterminal.com produces approximately 0.0g 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 5 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for 681busterminal.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.0g
RatingA
Page Weight & Optimization
HTML Size5 KB
CompressionGzip
Compression Savings~6.6%
CDNNo
Total Requests20
3rd Party Domains9
CSS Minified0/0
JS Minified0/3
681busterminal.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
681busterminal.com resolves to the IPv4 address 43.241.73.162, 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: ns169.pointdnshere.com and ns170.pointdnshere.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 681busterminal.com is handled by 681busterminal.com with 1 MX records configured: mail.681busterminal.com. 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 681busterminal.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 4 active subdomains for 681busterminal.com: ftp.681busterminal.com, mail.681busterminal.com, smtp.681busterminal.com, and www.681busterminal.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns169.pointdnshere.com
ns170.pointdnshere.com
Email & Authentication
MX Provider681busterminal.com
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (4 found)
ftp.681busterminal.com mail.681busterminal.com smtp.681busterminal.com www.681busterminal.com
681busterminal.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of 681busterminal.com contains 60 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 0 H2 headings, 0 H3 headings, 0 H4 headings.
The page includes 5 images. 2 images (40%) 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 60% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 3 internal links pointing to other pages on the same domain and 6 external links pointing to third-party websites. There are 3 external JavaScript files, 0 CSS stylesheets, and 0 iframes on the page.
Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
The website has social media presence across 1 platforms: Facebook (@681BusTerminal). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1—
H2 Tags0
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links3
External Links6
Assets & Features
JavaScript Files3
JS Minified0/3
CSS Files0
CSS Minified0/0
Iframes0
Images5
Missing Alt2
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Social Media Presence
Facebook: @681BusTerminal
681busterminal.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for 681busterminal.com is well-optimized at 36 characters: "681 Bus Terminal V2 - 681 �ڤh�`�� V2". 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 681busterminal.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 zh.
No Open Graph tags are configured. When someone shares a link to 681busterminal.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
681 Bus Terminal V2 - 681 �ڤh�`�� V2
https://681busterminal.com
Meta Tags
Title681 Bus Terminal V2 - 681 �ڤh�`�� V2...
Title Length36 chars
Meta Desc Length0 chars
H1—
Languagezh
Canonical—
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Type—
OG ImageNot set
Twitter Card—
FaviconNot set