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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations234 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- 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 Records4 A records, 32 ms lookupPASS
| A | 3.165.190.29, 3.165.190.15, 3.165.190.110, 3.165.190.129 |
| 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), 342 ms totalPASS
https://www.ifttt.com
204 ms · HTTP/1.1
https://ifttt.com/
138 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.ifttt.com | 301 | 204 ms | HTTP/1.1 | envoy |
| 2 | https://ifttt.com/ | 200 | 138 ms | HTTP/1.1 | envoy |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 13 URLsPASS
User-agent: *
Disallow: /user/new?return_to=*
Disallow: /search/query/
Disallow: /unsubscribe-from-applet/
Disallow: /unsubscribe
Disallow: /missing_link
Disallow: /create
Sitemap: https://ifttt.com/sitemap.xml
- https://ifttt.com/sitemap_general.xml
- https://ifttt.com/sitemap_explore.xml
- https://ifttt.com/sitemap_services.xml
- https://ifttt.com/sitemap_connect_pages....
- https://ifttt.com/sitemap_connect_pages1...
- https://ifttt.com/sitemap_connect_pages2...
- https://ifttt.com/sitemap_connect_pages3...
- https://ifttt.com/sitemap_connect_pages4...
- https://ifttt.com/sitemap_connect_pages5...
- https://ifttt.com/sitemap_applets.xml
- https://ifttt.com/sitemap_applets1.xml
- https://ifttt.com/sitemap_applets2.xml
- https://ifttt.com/sitemap_users.xml
A+Domain Intelligenceifttt.com — via GoDaddy.com, LLC, 16 years, 11 months oldPASS
2 days
July 14, 2026
234 days
Issued by Amazon
16 years, 11 months
Registered July 14, 2009
Not enabled
Protects against DNS spoofing
Unknown
2600:9000:273b:5200:1:b1c6:9e40:93a1
GoDaddy.com, LLC
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