Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNS Records2 A records, 5239 ms lookupREVIEW
| A | 192.200.160.253, 63.141.128.3 |
| AAAA | — |
| CNAME | www.bigcommerce.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)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations187 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
A+Redirect ChainNo redirects — direct accessPASS
https://www.bigcommerce.com
443 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.bigcommerce.com | 200 | 443 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 576 URLsPASS
# robots.txt for https://www.bigcommerce.com/
User-agent: deepcrawl
Disallow: /
User-agent: *
# Directories
Disallow: /includes/
Disallow: /misc/
Disallow: /modules/
Disallow: /profiles/
Disallow: /scripts/
Disallow: /themes/
Disallow: /mojocheck/
Disallow: /split/
# Files
Disallow: /CHANGELOG.txt
Disallow: /cron.php
Disallow: /INSTALL.mysql.txt
Disallow: /INSTALL.pgsql.txt
Disallow: /INSTALL.sqlite.txt
Disallow: /install.php
Disallow: /INSTALL.txt
Disallow: /LICENSE.txt
Disallow: /MAINTAINERS.txt
Disallow: /update.php
Disallow: /UPGRADE.txt
Disallow: /xmlrpc.php
Disallow: /index.php
# Paths (clean URLs)
Disallow: /admin/
Disallow: /hub/
Disallow: /comment/reply/
Disallow: /*filter=
Disallow: /?filter=
Disallow: /comment/
Disallow: /*price=
Disallow: /?price=
Disallow: /filter/tips/
Disallow: /node/add/
Disallow: /search/
Disallow: /user/
Disallow: /lp
# Paths (Don't index any unclean paths)
# Paths (Don't index any unclean paths)
Disallow: */?q=
Disallow: */?s=
Disallow: */?marketplaceCosts=
Disallow: */?ajs_aid=
Disallow: */?utm
Disallow: */?fl_
Disallow: */?industry=
Disallow: */?preview
Disallow: */?kme
Disallow: */?search=
Disallow: */s_id=
Disallow: */?costPlans=
Disallow: */?sort=
Disallow: */?collection=
Disallow: */?price=
Sitemap: https://www.bigcommerce.com/blog/sitemap-blog.xml
Sitemap: https://www.bigcommerce.com/apps/sitemap-marketplace-apps.xml
Sitemap: https://www.bigcommerce.com/apps/sitemap-marketplace-apps-categories.xml
Sitemap: https://www.bigcommerce.com/apps/sitemap-marketplace-apps-collections.xml
Sitemap: https://www.bigcommerce.com/theme/sitemap-marketplace-themes.xml
Sitemap: https://www.bigcommerce.com/theme/sitemap-marketplace-theme-industries.xml
Sitemap: https://www.bigcommerce.com/showcase/sitemap-showcase.xml
Sitemap: https://www.bigcommerce.com/sitemap-main.xml
Sitemap: https://www.bigcommerce.com/articles/sitemap-articles.xml
Sitemap: https://www.bigcommerce.com/press/sitemap-press.xml
Sitemap: https://www.bigcommerce.com/case-study/case-study.xml
Sitemap: https://www.bigcommerce.com/resources/resources.xml
Sitemap: https://www.bigcommerce.com/glossary/glossary-categories.xml
Sitemap: https://www.bigcommerce.com/glossary/glossary.xml
# Algolia-Crawler-Verif: 46E447DA7CAB443ABCE
- https://www.bigcommerce.com/blog/google-pay-app-webview-checkout/
- https://www.bigcommerce.com/blog/shipping-promotions-flexible-discounts-that-increase-conversions/
- https://www.bigcommerce.com/blog/b2b-merchants-cagr-study/
- https://www.bigcommerce.com/blog/attend-commerce-live/
- https://www.bigcommerce.com/blog/commerce-live-b2b/
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencebigcommerce.com — via SafeNames Ltd., 27 years, 6 months old, hosted on BIGCOMMERCE - Bigcommerce Inc., USPASS
576 days
February 8, 2028
187 days
Issued by DigiCert Inc
27 years, 6 months
Registered February 8, 1999
Not enabled
Protects against DNS spoofing
BIGCOMMERCE - Bigcommerce Inc., US
ASN AS399566
63.141.128.3
SafeNames Ltd.
Expiry timeline
Recommended actions
- 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