Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BHTTP Probe TimingTotal 948 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations56 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
A+DNS Records2 A records, 48 ms lookupPASS
| A | 172.66.139.129, 172.66.135.209 |
| AAAA | 2606:4700:10::ac42:8b81, 2606:4700:10::ac42:87d1 |
| CNAME | — |
| NS | rita.ns.cloudflare.com, joel.ns.cloudflare.com |
| MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 20 alt2.aspmx.l.google.com 30 aspmx4.googlemail.com 30 aspmx2.googlemail.com 30 aspmx5.googlemail.com 30 aspmx3.googlemail.com |
| TXT | SPF v=spf1 include:449646.spf03.hubspotemail.net include:_spf.google.com google-site-verification=gQg2veFevA00irNA4E4v-FxSJZ46caw-yFMt3MSsE3g google-site-verification=WE1K-7i0cG66D2aYLHVIBb4h67O1F105VrQNQO-jDbg mandrill_verify.k3DLhSmAlKMINXGJh-oRLw apple-domain-verification=YY5MnL4Gm2zHry4apZo7eLv7l9laRcre0S_EGJ6kRPU |
| 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.
ARedirect Chain1 redirect(s), 145 ms totalPASS
https://skift.com
68 ms · HTTP/1.1
https://skift.com/es/
78 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://skift.com | 302 | 68 ms | HTTP/1.1 | cloudflare |
| 2 | https://skift.com/es/ | 200 | 78 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
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
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 36 URLsPASS
User-agent: *
Disallow: /wp-content/uploads/*/*.pdf
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:
Sitemap: https://skift.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
- https://skift.com/post-sitemap.xml
- https://skift.com/post-sitemap2.xml
- https://skift.com/post-sitemap3.xml
- https://skift.com/post-sitemap4.xml
- https://skift.com/post-sitemap5.xml
- https://skift.com/post-sitemap6.xml
- https://skift.com/post-sitemap7.xml
- https://skift.com/post-sitemap8.xml
- https://skift.com/post-sitemap9.xml
- https://skift.com/post-sitemap10.xml
- https://skift.com/post-sitemap11.xml
- https://skift.com/post-sitemap12.xml
- https://skift.com/post-sitemap13.xml
- https://skift.com/post-sitemap14.xml
- https://skift.com/post-sitemap15.xml
- https://skift.com/post-sitemap16.xml
- https://skift.com/post-sitemap17.xml
- https://skift.com/post-sitemap18.xml
- https://skift.com/post-sitemap19.xml
- https://skift.com/post-sitemap20.xml
- https://skift.com/post-sitemap21.xml
- https://skift.com/post-sitemap22.xml
- https://skift.com/post-sitemap23.xml
- https://skift.com/post-sitemap24.xml
- https://skift.com/post-sitemap25.xml
- https://skift.com/post-sitemap26.xml
- https://skift.com/post-sitemap27.xml
- https://skift.com/post-sitemap28.xml
- https://skift.com/post-sitemap29.xml
- https://skift.com/page-sitemap.xml
- https://skift.com/insight-sitemap.xml
- https://skift.com/category-sitemap.xml
- https://skift.com/av_series-sitemap.xml
- https://skift.com/sk_author-sitemap.xml
- https://skift.com/sponsor-sitemap.xml
- https://skift.com/series-sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
ADomain Intelligenceskift.com — via GoDaddy.com, LLC, 22 years, 1 months oldPASS
30 days
July 16, 2026
56 days
Issued by Google Trust Services
22 years, 1 months
Registered July 16, 2004
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:10::ac42:87d1
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
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice