dbs.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of dbs.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 38283ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 337 KB, and the site is served behind a CDN (Content Delivery Network).
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 9 technologies across 8 categories powering dbs.com. The detected stack includes Next.js chunks, React, Bootstrap, Webpack, Google Analytics 4, LinkedIn Insight Tag, Mailchimp, jQuery 3.3.1., and Lodash. The site uses Next.js as its primary framework (version chunks). The UI is built with React.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, dbs.com receives an overall trust score of 75/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time38283ms
ProtocolHTTP/2
Page Size337 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests157
3rd Party Domains7
Redirect2 hop(s)
Detected Technologies (9)
🔧 Next.js
⚛️ React
🎨 Bootstrap
🔨 Webpack
📊 Google Analytics 4
📢 LinkedIn Insight Tag
📧 Mailchimp
📦 jQuery
📦 Lodash
Security Headers
✓
Content-Security-Policy
Set ✓
✓
Strict-Transport-Security (HSTS)
Set ✓
✓
X-Content-Type-Options
Set ✓
✗
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=R12
SubjectcommonName=dbs.com
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
dbs.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, dbs.com receives a trust score of 75/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 quarantine policy, and DNSSEC providing authenticated DNS responses.
Areas of concern include: the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved.
We checked dbs.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
✅ HSTS enabled
✅ SPF configured
✅ DMARC configured (p=quarantine)
✅ DNSSEC enabled
✅ Sitemap.xml found
✅ Robots.txt found
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
dbs.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned dbs.com and identified 9 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.
Framework: Next.js (version chunks) — provides the application framework and routing for dbs.com.
UI Library: React — handles the user interface rendering and component management for dbs.com.
CSS Framework: Bootstrap — provides the styling and responsive layout system for dbs.com.
Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for dbs.com.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for dbs.com.
Advertising: LinkedIn Insight Tag — handles advertising pixel tracking and conversion measurement for dbs.com.
Email Marketing: Mailchimp — manages email campaigns and subscriber lists for dbs.com.
JavaScript Library: jQuery (version 3.3.1.) and Lodash — provides utility functions and DOM manipulation for dbs.com.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-3C0CI. These IDs can be used to identify other websites operated by the same organization.
Framework
UI Library
CSS Framework
Build Tool
Analytics
📊 Google Analytics 4(95%)
Advertising
📢 LinkedIn Insight Tag(95%)
Email Marketing
JavaScript Library
📦 jQuery 3.3.1.(100%)📦 Lodash(95%)
Tracking IDs
dbs.com Performance, Speed & Core Web Vitals
🤖 AI Summary
dbs.com delivers its homepage in 38283ms (server response time), which is considered slow by industry standards. The total page weight is 337 KB, and we detected 157 resource requests loading assets from 7 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 7 CSS files and 3 out of 35 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.
The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors.
From an environmental perspective, each page view of dbs.com produces approximately 0.16g of CO₂, earning a carbon rating of B. 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 337 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for dbs.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.16g
RatingB
Page Weight & Optimization
HTML Size337 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests157
3rd Party Domains7
CSS Minified0/7
JS Minified3/35
dbs.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
dbs.com resolves to the IPv4 address 110.4.47.190, 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 2 A record(s) configured.
The domain name system is managed by 10 name servers: a1-7.akam.net, a26-67.akam.net, a9-65.akam.net, ns1.gdnsdef.com, ns3.gdnsdef.net, ns5.gdnsdef.net, ns7.gdnsdef.com, ns9.gdnsec.net, secdns.starhub.net.sg, and secdns2.starhub.net.sg. Having 10 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 dbs.com is handled by dbs.com with 5 MX records configured: mail4.dbs.com, mail4a.dbs.com, and mail6.dbs.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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic.
DNSSEC is enabled for dbs.com, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites.
Our subdomain enumeration scan discovered 2 active subdomains for dbs.com: webmail.dbs.com and www.dbs.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
a1-7.akam.net
a26-67.akam.net
a9-65.akam.net
ns1.gdnsdef.com
ns3.gdnsdef.net
ns5.gdnsdef.net
ns7.gdnsdef.com
ns9.gdnsec.net
secdns.starhub.net.sg
secdns2.starhub.net.sg
MX
mail4.dbs.com
mail4a.dbs.com
mail6.dbs.com
mail6a.dbs.com
mail5p.dbs.com
Email & Authentication
MX Providerdbs.com
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (2 found)
webmail.dbs.com www.dbs.com
dbs.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of dbs.com contains 537 words of visible text content. This is a moderate amount of content. The page is structured with 2 H2 headings, 1 H3 headings, 14 H4 headings, 1 H5, and 0 H6 headings.
The page includes 12 images. 1 images (8%) 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 92% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 64 internal links pointing to other pages on the same domain and 18 external links pointing to third-party websites. There are 35 external JavaScript files, 7 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 website has social media presence across 2 platforms: Facebook (@dbs) and Linkedin (@dbs-bank). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1AI-enabled bank with a heart
H2 Tags2
H3 Tags1
H4 Tags14
H5 Tags1
H6 Tags0
Internal Links64
External Links18
Assets & Features
JavaScript Files35
JS Minified3/35
CSS Files7
CSS Minified0/7
Iframes0
Images12
Missing Alt1
SitemapYes ✓
Robots.txtYes ✓
PWANo
AMPNo
RSS FeedNo
Social Media Presence
Facebook: @dbsLinkedin: @dbs-bank
dbs.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for dbs.com is well-optimized at 48 characters: "DBS: Trusted as the World’s Best Bank | DBS Bank". 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 dbs.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 canonical url is correctly set to https://www.dbs.com/default.page, preventing duplicate content issues, the meta robots directive is set to index,follow, and a favicon is configured.
No Open Graph tags are configured. When someone shares a link to dbs.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
DBS: Trusted as the World’s Best Bank | DBS Bank
https://dbs.com
Meta Tags
TitleDBS: Trusted as the World’s Best Bank | DBS Bank...
Title Length48 chars
Meta Desc Length0 chars
H1AI-enabled bank with a heart
Language—
Canonicalhttps://www.dbs.com/default.page
Meta Robotsindex,follow
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Type—
OG ImageNot set
Twitter Card—
FaviconSet ✓
dbs.com Related Domains & Cross-References
🤖 AI Summary
Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with dbs.com. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: ga4_id: G-3C0CI.
Tracking IDs for Cross-Referencing
Related Domains
Related domain data requires database (populated after batch crawl)