db.com

An authorized sender list is defined; mail from other servers is flagged as suspicious.

~all (softfail) — acceptable when combined with enforced DMARC. 0 of 10 DNS lookups.

v=spf1 ip4:160.83.0.0/16 ~all

$ dig +short TXT db.com

Forged email in the company's name is blocked by mail servers.

Policy p=reject.

v=DMARC1; p=reject; sp=reject; adkim=s; fo=1; ri=3600; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com,mailto:dmarc.reports@db.com

$ dig +short TXT _dmarc.db.com

A 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: s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.

s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0+M8/Lz0ZtrLs5gXWkzabVgY1enzaF6H…
s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDIjxMxkWNIlvKZLAYaln/NXr1caf7aED0C1jV1…

$ dig +short TXT s1._domainkey.db.com

Mail exchangers are published for the domain.

7 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.

10 smtp12.db.com
10 smtp14.db.com
10 smtp13.db.com
10 smtp24.db.com
10 smtp22.db.com
15 smtp23.db.com
10 smtp15.db.com

$ dig +short MX db.com

The site loads over an encrypted connection.

https://db.com/ returned HTTP 200 (final URL: https://www.db.com/). Client-side certificate validation passed.

HTTP 200
Final URL: https://www.db.com/

$ curl -sIL https://db.com/

Visitors arriving at an unencrypted address are automatically sent to the secure version.

HTTP 301 → https://db.com:443/

HTTP 301
Location: https://db.com:443/

$ curl -sI http://db.com/ | grep -iE "^(HTTP|location)"

The certificate was accepted by a validating TLS client at scan time.

Live TLS handshake succeeded. Latest issuance in CT logs: DigiCert, expiring 2027-06-01 (198 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: DigiCert
Valid from: 2026-11-15
Valid until: 2027-06-01
Names: db.com, prodredirect.db.com, www.db.com
Based on Certificate Transparency logs; may not reflect the certificate currently served.

$ echo | openssl s_client -connect db.com:443 -servername db.com 2>/dev/null | openssl x509 -noout -issuer -dates

Encryption enforcement is set for too short a time.

max-age=3600 (0 days), includeSubDomains. ≥ 180 days recommended.

Strict-Transport-Security: max-age=3600;includeSubDomains

$ curl -sIL https://db.com/ | grep -i "Strict-Transport-Security"

/*
  Strict-Transport-Security: max-age=31536000; includeSubDomains

Missing Content-Security-Policy header: this removes one layer of protection against script injection.

No Content-Security-Policy header found.

Content-Security-Policy: (missing)

$ curl -sIL https://db.com/ | grep -i "Content-Security-Policy"

/*
  Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'

The site can't be embedded by foreign sites.

X-Frame-Options: SAMEORIGIN

X-Frame-Options: SAMEORIGIN

$ curl -sIL https://db.com/ | grep -i "X-Frame-Options"

The browser won't guess file types in a way that could execute code.

nosniff is set.

X-Content-Type-Options: nosniff

$ curl -sIL https://db.com/ | grep -i "X-Content-Type-Options"

Internal URLs (including parameters) may leak to external sites.

Referrer-Policy is missing; the browser will use its default.

Referrer-Policy: (missing)

$ curl -sIL https://db.com/ | grep -i "Referrer-Policy"

/*
  Referrer-Policy: strict-origin-when-cross-origin

Access to sensitive features like the camera and location isn't restricted.

Missing Permissions-Policy header.

Permissions-Policy: (missing)

$ curl -sIL https://db.com/ | grep -i "Permissions-Policy"

/*
  Permissions-Policy: camera=(), microphone=(), geolocation=()

The 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://db.com/ | grep -iE "^(server|x-powered-by)"

The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.

No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.

AD = false
DS db.com: NODATA

$ dig +short DS db.com

dig +dnssec db.com SOA
delv db.com

Only authorized certificate authorities can issue certificates for the domain.

CAA records: 0 issue "amazon.com" | 0 issuewild ";" | 0 issue "quovadisglobal.com" | 0 issue "globalsign.com" | 0 issue "digicert.com"

0 issue "amazon.com"
0 issuewild ";"
0 issue "quovadisglobal.com"
0 issue "globalsign.com"
0 issue "digicert.com"

$ dig +short CAA db.com

The domain is served by several DNS servers, so one server failing won't take it down.

9 NS servers.

ns11.db-dns.com
ns13.db-dns.com
ns15.db-dns.com
ns10.db-dns.de
ns12.db-dns.de
ns14.db-dns.de
ns2.db-dns.com
ns1.db-dns.de
ns3.db-dns.de

$ dig +short NS db.com