Digital exposure report
dbs.com.sg
Low exposure. The domain is well protected in most areas checked.
Scanned: 2026-11-22 15:02 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Choose which companies may issue certificates for your domain
This reduces the chance of a certificate being issued by a provider you did not choose.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short CAA dbs.com.sg
- 2.
Turn off browser features your site does not use
This limits access to things like camera or location if a page is misused.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://dbs.com.sg/ | grep -i "Permissions-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- dbs.com.sg
- Website request
- GET https://dbs.com.sg/ → https://www.dbs.com.sg/index/default.page
- Scan time
- 2026-11-22 15:02:40 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 29/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 26/30 | The site instructs browsers to block common attacks. |
| DNS infrastructure | 10/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.LowCAA — who may issue certificates · Hardening gap+5
- 2.LowPermissions-Policy · Hardening gap+2
- 3.LowReferrer-Policy · Hardening gap+2
- 4.LowDMARC — anti-spoofing policy · Hardening gap+1
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 0 of the 10 allowed DNS lookups.
v=spf1 -all
$ dig +short TXT dbs.com.sg
DMARC — anti-spoofing policy
Needs attention · Severity: Low · Hardening gap · 14/15Forged email in the company's name is blocked by mail servers.
Policy p=reject. No rua — no reports on spoofing attempts are received.
v=DMARC1; p=reject; fo=1; ruf=mailto:dmarc@dbs.com
$ dig +short TXT _dmarc.dbs.com.sg
- Keep your current p=reject enforcement and edit the existing record in place — do not replace it with p=none.
- Add rua=mailto:… to the existing record so you receive aggregate reports. Nothing else changes.
_dmarc.dbs.com.sg. TXT "v=DMARC1; p=reject; fo=1; ruf=mailto:dmarc@dbs.com; rua=mailto:dmarc@dbs.com.sg"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Your domain already enforces DMARC. Edit the record in place; never roll back to p=none.
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: dkim. Confirm signing with dkim=pass in a sent message's Authentication-Results.
dkim._domainkey: v=DKIM1; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxmx12AvodeRmGbsiTJw3YfitnbzCGMke7yU…
$ dig +short TXT dkim._domainkey.dbs.com.sg
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
3 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
5 mail4.dbs.com 5 mail6.dbs.com 20 mail5p.dbs.com
$ dig +short MX dbs.com.sg
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://dbs.com.sg/ returned HTTP 200 (final URL: https://www.dbs.com.sg/index/default.page). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.dbs.com.sg/index/default.page
$ curl -sIL https://dbs.com.sg/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://dbs.com.sg/
HTTP 301 Location: https://dbs.com.sg/
$ curl -sI http://dbs.com.sg/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: GlobalSign, expiring 2027-04-15 (143 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: GlobalSign Valid from: 2026-09-28 Valid until: 2027-04-15 Names: dbs.com.sg, www.dbs.com, www.dbs.com.sg Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect dbs.com.sg:443 -servername dbs.com.sg 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
$ curl -sIL https://dbs.com.sg/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Passed · Severity: OK · 8/8The site restricts which scripts are allowed to run.
CSP is set without permissive sources in script-src.
Content-Security-Policy: default-src 'self' https://www.dbs.com.sg https://www.prv.dbs.com.sg https://dbsweb-u03-www.dbs.com.sg https://chatbanking-uat.dbs.com https://chatbanking.dbs.com wss: https: data:; object-src 'none' ; img-src 'self' https://www.dbs.com.sg https://dbsweb-u03-www.dbs.com.sg https://dbsweb-u01-www-prv.dbs.com.sg data: https:; script-src 'nonce-798e264d-f6db-4432-ad55-02d4da711473' 'strict-dynamic'; style-src 'self' 'unsafe-inline' https://chatbanking-uat.dbs.com https://chatbanking.dbs.com; frame-src 'self' https://www.youtube.com/; script-src-elem 'self' 'unsafe-inline' https://assets.adobedtm.com https://chatbanking-uat.dbs.com https://chatbanking.dbs.com https://safe2.dbswiso.prd https://safe1.dbswiso.prd;
$ curl -sIL https://dbs.com.sg/ | grep -i "Content-Security-Policy"
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: DENY
X-Frame-Options: DENY
$ curl -sIL https://dbs.com.sg/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://dbs.com.sg/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Needs attention · Severity: Low · Hardening gap · 1/3The policy sends full URLs to external sites.
Referrer-Policy: no-referrer-when-downgrade — sends the full URL including path and query.
Referrer-Policy: no-referrer-when-downgrade
$ curl -sIL https://dbs.com.sg/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://dbs.com.sg/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://dbs.com.sg/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec dbs.com.sg | grep -E "flags:.* ad"
CAA — who may issue certificates
Needs attention · Severity: Low · Hardening gap · 0/5Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.
No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.
(no CAA records found)
$ dig +short CAA dbs.com.sg
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
dbs.com.sg. CAA 0 issue "letsencrypt.org" dbs.com.sg. CAA 0 iodef "mailto:security@dbs.com.sg"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
10 NS servers.
ns1.gdnsdef.com ns3.gdnsdef.net ns5.gdnsdef.net ns7.gdnsdef.com ns9.gdnsec.net a1-7.akam.net a9-65.akam.net a26-67.akam.net secdns.starhub.net.sg secdns2.starhub.net.sg
$ dig +short NS dbs.com.sg
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rules1 observed gaps
- PCI DSS v4.0No gaps observed
- NIS2 / vendor due diligence2 observed gaps
- SOC 2 / ISO 27001 baseline1 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | dbs.com.sg | 103.7.8.138 | 110.4.47.190 |
| AAAA | dbs.com.sg | — |
| MX | dbs.com.sg | 5 mail4.dbs.com | 5 mail6.dbs.com | 20 mail5p.dbs.com |
| NS | dbs.com.sg | ns1.gdnsdef.com | ns3.gdnsdef.net | ns5.gdnsdef.net | ns7.gdnsdef.com | ns9.gdnsec.net | a1-7.akam.net | a9-65.akam.net | a26-67.akam.net | secdns.starhub.net.sg | secdns2.starhub.net.sg |
| TXT | dbs.com.sg | v=spf1 -all | MS=ms52461009 | _0532b03v05bx1jccae3k7k9er9rqakh | _kzjrdt3lxtidxbmg61dif2fax6exsj8 | _lje2cqb396sk7py7uwbhq6sd4g8we1y | C08A-DE8A-562F-B518-68E4-EDC9-94DE-1642 | facebook-domain-verification=47486dzbv0j3tnwafx4h4oravretdb | google-site-verification=QXKk9JlVokcPRvpJFO2O7Hy9yxfZ9fG19rrew_QlJy0 | _globalsign-domain-verification=D7QUOp08E9Xp8AZ3vp-OYiOjZrTpbdPwvCaS7gHgnj | _globalsign-domain-verification=EhbkS3UefxpHxr1NMs4xqS9DhkfAplVvjKBBudvRIo | _globalsign-domain-verification=wgnnWG6A68yazE6COlu_p79WnAfIo5lKSIBsIHeaY7 |
| TXT | _dmarc.dbs.com.sg | v=DMARC1; p=reject; fo=1; ruf=mailto:dmarc@dbs.com |
| CAA | dbs.com.sg | — |
| DS | dbs.com.sg | 56654 8 2 a2469065c476a93bbd202267b8b3cdc4c139185e985f9597d6919f157579a39c |