DNS & Email Security Report for bnpparibas.com

An automated analysis of bnpparibas.com's DNS configuration, email authentication (SPF, DKIM, DMARC), DNSSEC chain, IPv6 readiness, and transport security. Last analyzed June 10, 2026.

C79/100
Average

Adequate security, improvements recommended

Overall security score: 79/100 · Grade C (Average)

This report is a cached snapshot

DNS changes frequently. Run a fresh, interactive scan of bnpparibas.com for live records, propagation, and deep checks.

Run a fresh live scan

Detailed check results

DNS

100%pass
  • A record presentcritical

    1 A record(s) found

  • AAAA record presentrecommended

    2 AAAA record(s) found

  • MX records presentrecommended

    1 MX record(s) found

  • NS records presentcritical

    5 NS record(s) found

  • SOA record presentcritical

    SOA record found

  • Multiple nameserversrecommended

    5 nameservers configured ✓

  • SOA serial formatinfo

    Serial 21512 (valid, managed DNS format)

  • SOA timers validinfo

    Refresh: 14400s ✓, Retry: 3600s ✓, Expire: 2419200s ✓

  • No lame nameserversinfo

    5 NS all responding ✓

  • Glue records presentinfo

    7 glue record(s)

  • WWW record configuredinfo

    CNAME record matches apex

  • MX servers have PTR recordsinfo

    1 MX IPs all have PTR records ✓

  • MX servers have FCrDNSinfo

    1 MX IPs have forward-confirmed reverse DNS ✓

DNSSEC

100%pass
  • DNSSEC signedrecommended

    DNSSEC is enabled ✓

  • DNSSEC validation OKcritical

    DNSSEC validates correctly ✓

  • NSEC3 RFC 9276 compliantrecommended

    NSEC3 iterations=0, salt=empty — RFC 9276 compliant ✓

  • RRSIG signatures validrecommended

    RRSIG signature expires in 2 days — renewal needed

  • 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 ✓

IPv6

70%warning
  • Website reachable via IPv6recommended

    2 AAAA record(s) ✓

  • Mail servers reachable via IPv6recommended

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

  • Nameservers reachable via IPv6recommended

    4/5 NS server(s) with IPv6 ✓

Email security

83%pass
  • SPF record presentcritical

    v=spf1 include:pns._spf.bnpparibas.com include:t._spf.bnpparibas.com include:o._spf.bnpparibas.com -all

  • SPF syntax validcritical

    SPF syntax is correct ✓

  • SPF policy strict (-all)recommended

    SPF uses -all (hard fail) ✓

  • DKIM foundrecommended

    DKIM selector: s1 ✓

  • DMARC record presentrecommended

    v=DMARC1; p=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]

  • DMARC policy quarantine or betterrecommended

    DMARC policy: reject ✓

  • DMARC policy rejectoptional

    DMARC policy: reject ✓

  • BIMI record presentoptional

    BIMI logo: https://vmc.digicert.com/9f16be0b-5073-4864-8986-2777d1dec819.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

    0/1 MX domain(s) have DNSSEC. Ask your mail provider to enable DNSSEC

  • MX DNSSEC validation OKrecommended

    DNSSEC not enabled for MX domains

  • Mail servers not blacklistedcritical

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

  • No critical blacklist listingscritical

    No blacklist listings ✓

Web security

45%fail
  • CAA records presentrecommended

    7 CAA record(s) ✓

  • CAA policy strictoptional

    CAA limits certificate authorities ✓

  • TLSA records (DANE)optional

    No TLSA/DANE records. Add TLSA at _25._tcp.mail for DANE email encryption

  • DANE configuration validoptional

    No DANE configured

  • No sensitive info in TXTcritical

    No sensitive data leaked ✓

  • Verification records reviewedinfo

    6 verification records found (Google, Zoom, Microsoft 365, Atlassian, DocuSign...). Review these - they reveal your tech stack to attackers. Remove unused service verifications

  • HTTPS availablecritical

    HTTPS working (status 403) ✓

  • Valid certificatecritical

    Certificate chain is valid and trusted ✓

  • HTTP redirects to HTTPScritical

    HTTP does not redirect to HTTPS. Add redirect in web server config

  • HSTS enabledrecommended

    HSTS enabled (max-age=600) ✓

  • HSTS max-age >= 1 yearoptional

    max-age=600 is too short. Set to 31536000 (1 year) or higher

  • X-Frame-Options headerrecommended

    No X-Frame-Options header. Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking

  • X-Content-Type-Options headerrecommended

    No X-Content-Type-Options header. Add X-Content-Type-Options: nosniff to prevent MIME sniffing

  • Content-Security-Policy headerrecommended

    No Content-Security-Policy header. Add CSP to prevent XSS and other injection attacks

  • Referrer-Policy headerrecommended

    No Referrer-Policy header. Add Referrer-Policy: strict-origin-when-cross-origin

  • security.txt presentoptional

    No security.txt. Create /.well-known/security.txt with Contact and Expires fields (RFC 9116)

  • security.txt validoptional

    No security.txt configured

  • HTTP/3 (QUIC) supportedoptional

    No HTTP/3 support detected No h3 in Alt-Svc header No HTTPS DNS record (type 65) QUIC probe inconclusive (Inconclusive - no QUIC reply (trigger may be dropped or UDP/443 filtered)) — not a negative signal

  • 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: bnpparibas.com IN HTTPS 1 . alpn="h3,h2"

Issues found (3)

Mail servers have no IPv6

Your mail servers are not reachable via IPv6

Learn more

Excessive verification TXT records

Your domain has many third-party verification records. These reveal your tech stack to potential attackers (reconnaissance). Review and remove unused verifications

Learn more

No HTTP/3 (QUIC) support

HTTP/3 uses QUIC for faster, more resilient connections. Enable it on your web server and open UDP/443 in your firewall

Learn more

Recommendations (3)

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

Enable HTTP/3 (QUIC)

Enable HTTP/3 for faster page loads and improved connection resilience. Nginx: add "listen 443 quic reuseport;" and "add_header Alt-Svc 'h3=":443"; ma=86400'". Caddy: HTTP/3 is enabled by default. Cloudflare: Enable under Speed → Protocol Optimization. Also add an HTTPS DNS record: example.com IN HTTPS 1 . alpn="h3,h2" Ensure UDP port 443 is open in your firewall (QUIC uses UDP, not TCP).

Impact: Faster page loads (0-RTT), better mobile performance, and connection migration between networks

About this report

IntoDNS.AI evaluates bnpparibas.com against DNS hygiene, email authentication, and transport-security best practices, scoring each check and rolling them up into an overall grade. Results reflect public DNS as observed on June 10, 2026 and may differ from a live scan if the domain has since changed its configuration.

Want to check your own domain? Scan any domain on the homepage.

Last analyzed: June 10, 2026 · Google Public DNS