Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1425 ms totalFIX
https://www.plaid.com
302 ms · HTTP/1.1
https://plaid.com/
281 ms · HTTP/1.1
https://plaid.com/en-eu/
843 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.plaid.com | 301 | 302 ms | HTTP/1.1 | AmazonS3 |
| 2 | https://plaid.com/ | 302 | 281 ms | HTTP/1.1 | CloudFront |
| 3 | https://plaid.com/en-eu/ | 200 | 843 ms | HTTP/1.1 | AmazonS3 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
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 & Recommendations189 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 Records4 A records, 38 ms lookupPASS
| A | 143.204.55.33, 143.204.55.111, 143.204.55.103, 143.204.55.109 |
| AAAA | — |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| 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+Crawlabilityrobots.txt present, sitemap with 1797 URLsPASS
User-agent: *
# Allow Images
Allow: *.png
Allow: *.svg
# PDFs
Disallow: *.pdf
# Folders / Pages / Parameters
Disallow: /legacy-docs/
Disallow: /*?*
Disallow: /api/*
Disallow: /contact/sales/*
Disallow: /docs-beta/*
Disallow: /sandbox/*
Disallow: /engineering
Disallow: /link/*
Disallow: /lending/
Disallow: /mortgage/*
Disallow: /new-plaid-docs/
Disallow: /plaiderdays/
Disallow: /unsubscribed/
Disallow: /errors/*
Disallow: /ai_day_docs/*
# Blog
Disallow: /blog/tag/*
Disallow: /blog/page/*
Disallow: /blog/undefined/*
Sitemap: https://plaid.com/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligenceplaid.com — via Gandi SAS, 31 years, 1 months oldPASS
33 days
August 15, 2026
189 days
Issued by Amazon
31 years, 1 months
Registered August 16, 1995
Not enabled
Protects against DNS spoofing
Unknown
2600:9000:273b:2400:1d:e80d:8080:93a1
Gandi 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