DNS & Email Security Report for siemens.com

• A record presentcritical

  2 A record(s) found

• AAAA record presentrecommended

  No AAAA records

• MX records presentrecommended

  1 MX record(s) found

• NS records presentcritical

  8 NS record(s) found

• SOA record presentcritical

  SOA record found

• Multiple nameserversrecommended

  8 nameservers configured ✓

• SOA serial formatinfo

  Serial 2026060929 (YYYYMMDDnn format)

• SOA timers validinfo

  Refresh: 3600s ✓, Retry: 600s ✓, Expire: 604800s ✓

• No lame nameserversinfo

  8 NS all responding ✓

• Glue records presentinfo

  No glue needed

• WWW record configuredinfo

  A: 18.239.105.125

• MX servers have PTR recordsinfo

  4 MX IPs all have PTR records ✓

• MX servers have FCrDNSinfo

  4 MX IPs have forward-confirmed reverse DNS ✓

• DNSSEC signedrecommended

  DNSSEC is enabled ✓

• DNSSEC validation OKcritical

  DNSSEC validates correctly ✓

• NSEC3 RFC 9276 compliantrecommended

  NSEC3 not RFC 9276 compliant: iterations=10 (must be 0), salt="8af7570bc0ceffe3" (must be empty). Modern resolvers may reject this zone

• RRSIG signatures validrecommended

  RRSIG signatures valid, earliest expiry in 29 days ✓

• Modern DNSSEC algorithmoptional

  RSA/SHA-256 (algorithm 8) — acceptable ✓

• DS digest algorithm modernrecommended

  DS digest: SHA-256 — modern ✓

• DNSKEY algorithm secureoptional

  DNSKEY: RSA/SHA-256 — acceptable, consider ECDSA (13) or Ed25519 (15)

• RRSIG TTL saferecommended

  Record TTLs do not exceed RRSIG validity periods ✓

• Chain of trust completecritical

  Complete chain: DNSKEY + DS + RRSIG ✓

• Website reachable via IPv6recommended

  No IPv6 for website. Add AAAA record pointing to your IPv6 address

• Mail servers reachable via IPv6recommended

  0/1 MX servers have IPv6. Add AAAA records for your mail servers

• Nameservers reachable via IPv6recommended

  8/8 NS server(s) with IPv6 ✓

• SPF record presentcritical

  v=spf1 exists:%{i}.spf.siemens.com include:spf.protection.outlook.com include:all.spf.avature.net include:mail.zendesk.com -all

• SPF syntax validcritical

  SPF syntax is correct ✓

• SPF policy strict (-all)recommended

  SPF uses -all (hard fail) ✓

• DKIM foundrecommended

  DKIM selector: selector1 ✓

• DMARC record presentrecommended

  v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; aspf=r

• DMARC policy quarantine or betterrecommended

  DMARC policy: reject ✓

• DMARC policy rejectoptional

  DMARC policy: reject ✓

• BIMI record presentoptional

  BIMI logo: https://assets.new.siemens.com/siemens/assets/api/uuid:01254302-7a71-4d1a-ac30-3698acc43591/siemensag2026new.svg

• BIMI configuration validoptional

  BIMI correctly configured ✓

• MTA-STS record presentoptional

  No MTA-STS. Add TXT at _mta-sts and host policy at /.well-known/mta-sts.txt

• MTA-STS policy enforcedoptional

  MTA-STS not configured

• MX records validcritical

  1 MX record(s) ✓

• MX domains use DNSSECrecommended

  1/1 MX domain(s) use DNSSEC ✓

• MX DNSSEC validation OKrecommended

  MX DNSSEC validates correctly ✓

• Mail servers not blacklistedcritical

  1 MX server(s) checked against 16 blacklists - clean ✓

• No critical blacklist listingscritical

  No blacklist listings ✓

• CAA records presentrecommended

  No CAA records. Add CAA record to specify allowed certificate authorities

• CAA policy strictoptional

  CAA not strict. Add CAA 0 issue "letsencrypt.org" (or your CA) to restrict issuance

• TLSA records (DANE)optional

  6 DANE record(s) - configured according to best practices

• DANE configuration validoptional

  DANE records meet best practices ✓

• No sensitive info in TXTcritical

  No sensitive data leaked ✓

• Verification records reviewedinfo

  11 verification records found (Adobe Sign, Facebook/Meta, Apple, Docker, OneTrust...). Review these - they reveal your tech stack to attackers. Remove unused service verifications

• HTTPS availablecritical

  HTTPS working (status 200) ✓

• Valid certificatecritical

  Certificate chain is valid and trusted ✓

• HTTP redirects to HTTPScritical

  HTTP automatically redirects to HTTPS ✓

• HSTS enabledrecommended

  HSTS enabled (max-age=31536000, includeSubDomains, preload) ✓

• HSTS max-age >= 1 yearoptional

  max-age=31536000 (≥1 year) ✓

• X-Frame-Options headerrecommended

  X-Frame-Options: sameorigin ✓

• X-Content-Type-Options headerrecommended

  X-Content-Type-Options: nosniff ✓

• Content-Security-Policy headerrecommended

  Content-Security-Policy configured ✓

• Referrer-Policy headerrecommended

  Referrer-Policy: strict-origin-when-cross-origin ✓

• security.txt presentoptional

  Contact: mailto:[email protected]

• security.txt validoptional

  security.txt has required Contact and Expires fields ✓

• HTTP/3 (QUIC) supportedoptional

  HTTP/3 (QUIC v1) on port 443 Detection methods: QUIC probe: inconclusive (no reply — trigger may be dropped or UDP/443 filtered) Alt-Svc header: h3=":443" Cache: 24h (ma=86400)

• QUIC UDP reachableinfo

  QUIC probe inconclusive (no reply — trigger may be dropped or UDP/443 filtered). Not a negative signal; h3 is judged from Alt-Svc / HTTPS record

• HTTPS DNS record (SVCB)optional

  No HTTPS DNS record (type 65). Add HTTPS record for faster HTTP/3 discovery: siemens.com IN HTTPS 1 . alpn="h3,h2"

Add IPv6 support

Request AAAA records from your hosting provider for your website. IPv6 is becoming increasingly important.

Impact: Makes your website accessible to IPv6-only networks

Add CAA records

Define which Certificate Authorities may issue SSL certificates, for example: "0 issue letsencrypt.org"

Impact: Prevents unauthorized certificate issuance

IPv6 for mail servers

Add AAAA records for your MX servers to support email via IPv6.

Impact: Improves email reachability for IPv6 networks

Review verification TXT records

Your domain has many third-party verification records that reveal your tech stack (Google, Microsoft, Atlassian, etc.). Review each one: 1) Remove records for services no longer used 2) Consider if each service really needs domain verification 3) Use a subdomain for less critical services. This is an information disclosure issue - attackers can map your SaaS footprint.

Impact: Reduces reconnaissance surface and limits attacker knowledge of your infrastructure