Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BTLS Certificate Expiry & Recommendations82 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
ADNS Records2 A records, 32 ms lookupPASS
| A | 172.64.150.216, 104.18.37.40 |
| AAAA | 2606:4700:440c::6812:2528, 2a06:98c1:310a::ac40:96d8 |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | hubspot-developer-verification=ZjE3M2UzYzYtY2I5OS00ZWNkLTlhZTItZjZhNDc4NzgxM2Ix hubspot-developer-verification=Yzg5OGFkYTQtZWRhOS00YWEzLWE5MjMtZDA2YTBlODRmMDlk hubspot-developer-verification=NjY1ZDc2YjgtY2IzYi00OWMxLWE1M2UtZTViNTc3ODcxN2U1 hubspot-developer-verification=YjYwNGVmYTgtYjBlOS00MjZmLWJmNDItMjMxYjQ0ZjJmOTI1 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Redirect ChainNo redirects — direct accessPASS
https://www.brevo.com
73 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.brevo.com | 200 | 73 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (16 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 6 URLsPASS
# Robots.txt for Brevo
# This file is used to manage how search engines index your site.
User-agent: *
Disallow: /integrations-p2/
Disallow: /glossary-p2/
Disallow: /enterprise-p2/
Disallow: /contact-p2/
Disallow: /partners/
# Block dynamic files and unwanted parameters
Disallow: /*-p2/ # Block all "-p2" pages
Disallow: /*.pdf$ # Block all .pdf files
Disallow: /404 # Block custom 404 pages
Disallow: /500 # Block custom 500 error pages
# Block preview mode (Next.js Preview Mode)
Disallow: /api/
Disallow: /api/preview/
# Block crawlers (waybackmachine) from all DE URLs
User-agent: ia_archiver
Disallow: /de/
User-agent: archive.org_bot
Disallow: /de/
User-agent: special_archiver
Disallow: /de/
User-agent: Heritrix
Disallow: /de/
# Sitemap Locations for Multi-Language Setup
Sitemap: https://www.brevo.com/sitemap.xml
Sitemap: https://www.brevo.com/sitemap_en.xml
Sitemap: https://www.brevo.com/sitemap_es.xml
Sitemap: https://www.brevo.com/sitemap_pt.xml
Sitemap: https://www.brevo.com/sitemap_it.xml
Sitemap: https://www.brevo.com/sitemap_fr.xml
Sitemap: https://www.brevo.com/sitemap_de.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencebrevo.com — via OVH sas, 26 years, 11 months oldPASS
86 days
September 10, 2026
82 days
Issued by Google Trust Services
26 years, 11 months
Registered September 10, 1999
Not enabled
Protects against DNS spoofing
Unknown
2a06:98c1:3200::90:81
OVH sas
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable DNSSEC to protect visitors from DNS spoofing
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033