Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNS Records2 A records, 35 ms lookupREVIEW
| A | 104.18.2.179, 104.18.3.179 |
| AAAA | 2606:4700::6812:2b3, 2606:4700::6812:3b3 |
| CNAME | www.databricks.com.cdn.cloudflare.net |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
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)
BTLS Certificate Expiry & Recommendations66 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+Redirect ChainNo redirects — direct accessPASS
https://www.databricks.com
158 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.databricks.com | 200 | 158 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 17 URLsPASS
User-agent: *
Allow: /
Sitemap: https://www.databricks.com/webshared/sitemaps/sitemap-index.xml
Host: https://www.databricks.com
- https://www.databricks.com/en-website-as...
- https://www.databricks.com/dataaisummit/...
- https://www.databricks.com/careers-asset...
- https://www.databricks.com/legal-assets/...
- https://www.databricks.com/en-resources-...
- https://www.databricks.com/en-blog-asset...
- https://www.databricks.com/blog-legacy-a...
- https://www.databricks.com/ja-blog-asset...
- https://www.databricks.com/br-blog-asset...
- https://www.databricks.com/ko-blog-asset...
- https://www.databricks.com/en-customer-a...
- https://www.databricks.com/en-partners-a...
- https://www.databricks.com/press-release...
- https://www.databricks.com/glossaries-as...
- https://www.databricks.com/trainings-ass...
- https://www.databricks.com/en-demo-cente...
- https://www.databricks.com/en-pricing-as...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencedatabricks.com — via Amazon Registrar, Inc., 14 years, 11 months oldPASS
30 days
July 13, 2026
66 days
Issued by DigiCert Inc
14 years, 11 months
Registered July 13, 2011
Enabled
Protects against DNS spoofing
Unknown
2a04:4e42:e00::740
Amazon Registrar, Inc.
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry