Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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 & Recommendations48 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
ADNS Records2 A records, 14 ms lookupPASS
| A | 172.64.150.145, 104.18.37.111 |
| 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)
ARedirect Chain1 redirect(s), 794 ms totalPASS
https://www.make.com
305 ms · HTTP/1.1
https://www.make.com/en
489 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.make.com | 301 | 305 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.make.com/en | 200 | 489 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 10 URLsPASS
# *
User-agent: *
Allow: /
Disallow: /en/hq*
Disallow: /en/integration/*
Disallow: /en/template/*
Disallow: /en/integrations/*/*/*
Disallow: /docs/old/*
# Host
Host: https://www.make.com/en
# Sitemaps
Sitemap: https://www.make.com/en/sitemap.xml
Sitemap: https://www.make.com/en/sitemap-0.xml
Sitemap: https://www.make.com/en/pw-api/sitemaps/blogs-sitemap.xml
Sitemap: https://www.make.com/en/pw-api/sitemaps/integrations-sitemap.xml
Sitemap: https://www.make.com/en/pw-api/sitemaps/templates-sitemap.xml
Sitemap: https://www.make.com/en/pw-api/sitemaps/how-to-guides-sitemap.xml
Sitemap: https://www.make.com/en/pw-api/sitemaps/success-stories-sitemap.xml
Sitemap: https://www.make.com/en/pw-api/sitemaps/webinars-sitemap.xml
Sitemap: https://www.make.com/en/pw-api/sitemaps/automate-sitemap.xml
Sitemap: https://www.make.com/en/pw-api/sitemaps/authors-sitemap.xml
Sitemap: https://www.make.com/en/pw-api/sitemaps/careers-sitemap.xml
- https://www.make.com/en/sitemap-0.xml
- https://www.make.com/en/pw-api/sitemaps/...
- https://www.make.com/en/pw-api/sitemaps/...
- https://www.make.com/en/pw-api/sitemaps/...
- https://www.make.com/en/pw-api/sitemaps/...
- https://www.make.com/en/pw-api/sitemaps/...
- https://www.make.com/en/pw-api/sitemaps/...
- https://www.make.com/en/pw-api/sitemaps/...
- https://www.make.com/en/pw-api/sitemaps/...
- https://www.make.com/en/pw-api/sitemaps/...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencemake.com — via united-domains GmbH, 29 years, 1 months old, hosted on CloudflarePASS
17 days
July 30, 2026
48 days
Issued by Let's Encrypt
29 years, 1 months
Registered July 31, 1997
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.18.37.111
united-domains GmbH
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