Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 183 ms totalREVIEW
https://wikihow.com
5 ms · HTTP/1.1
https://www.wikihow.com/
47 ms · HTTP/1.1
https://www.wikihow.com/Main-Page
131 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://wikihow.com | 301 | 5 ms | HTTP/1.1 | |
| 2 | https://www.wikihow.com/ | 301 | 47 ms | HTTP/1.1 | |
| 3 | https://www.wikihow.com/Main-Page | 200 | 131 ms | HTTP/1.1 |
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
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
BCrawlabilityrobots.txt present, sitemap with 33961 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# robots.txt for wikiHow
# based on wikipedia.org's robots.txt
#
# Crawlers that are kind enough to obey, but which we'd rather not have
# unless they're feeding search engines.
# Sitemap: https://www.wikihow.com/sitemap_index.xml
# Or: /sitemap.xml on some other domains.
#
# If your bot supports such a thing using the 'Crawl-delay' or another
# instruction, we can add it to our robots.txt.
#
# Friendly, low-speed bots are welcome viewing article pages, but not
# dynamically-generated pages please. Article pages contain our site's
# real content.
#
# NOTICE: All crawlers and bots, regardless of whether or not they are
# specified below, are strictly prohibited from using our content for the
# purposes of training or retrieval for AI models or similar machine learning
# systems, except where explicit prior permission has been granted by wikiHow
# through a contractual licensing agreement. Any use of our content for such
# purposes without our explicit contractual permission is a violation of our
# terms of service and intellectual property rights.
User-agent: Ai2Bot
Disallow: /
User-agent: AI2Bot
Disallow: /
User-agent: Ai2Bot-Dolma
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: archive.org
Disallow: /api.php
Disallow: /index.php
Disallow: /Special:
User-agent: Applebot-Extended
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Claude-SearchBot
Disallow: /
User-agent: Claude-User
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: cohere-ai
Disallow: /
User-agent: Diffbot
Disallow: /
User-agent: DOC
Disallow: /
User-agent: Download Ninja
Disallow: /
User-agent: DuckAssistBot
Disallow: /
User-agent: FacebookBot
Disallow: /
User-agent: Facebookexternalhit
Disallow: /
User-agent: FriendlyCrawler
Disallow: /
User-agent: Fetch
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: GrokApp
Disallow: /
User-agent: HMSE_Robot
Disallow: /
User-agent: HTTrack
Disallow: /
User-agent: ia_archiver
Disallow: /
User-agent: ICC-Crawler
Disallow: /
User-agent: ImagesiftBot
Disallow: /
User-agent: img2dataset
Disallow: /
User-agent: k2spider
Disallow: /
User-agent: larbin
Disallow: /
User-agent: libwww
Disallow: /
User-agent: linko
Disallow: /
User-agent: Meta-ExternalAgent
Disallow: /
User-agent: Meta-ExternalFetcher
Disallow: /
User-agent: Meta-WebIndexer
Disallow: /
User-agent: Microsoft.URL.Control
Disallow: /
User-agent: MistralAI-User
Disallow: /
User-agent: MSIECrawler
Disallow: /
# Requests many pages per second
# http://www.nameprotect.com/botinfo.html
User-agent: NPBot
Disallow: /
User-agent: OAI-SearchBot
Disallow: /
User-agent: Offline Explorer
Disallow: /
User-agent: omgili
Disallow: /
User-agent: OmigiliBot
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: PetalBot
Disallow: /
User-agent: Scrapy
Disallow: /
User-agent: Seekr
Disallow: /
# Some bots are known to be trouble, particularly those designed to copy
# entire sites. Please obey robots.txt.
User-agent: sitecheck.internetseer.com
Disallow: /
User-agent: SiteSnagger
Disallow: /
User-agent: Teleport
Disallow: /
User-agent: TeleportPro
Disallow: /
User-agent: TikTokSpider
Disallow: /
User-agent: Timpibot
Disallow: /
User-agent: UbiCrawler
Disallow: /
User-agent: VelenPublicWebCrawler
Disallow: /
User-agent: WebCopier
Disallow: /
User-agent: WebReaper
Disallow: /
User-agent: WebStripper
Disallow: /
User-agent: Webzio-Extended
Disallow: /
User-agent: WebZIP
Disallow: /
# wget in recursive mode uses too many resources for us.
# Please read the man page and use it properly; there is a
# --wait option you can use to set the delay between hits,
# for instance. Please wait 3 seconds between each request.
User-agent: wget
Disallow: /
User-agent: Xenu
Disallow: /
User-agent: YouBot
Disallow: /
User-agent: Zao
Disallow: /
User-agent: Zealbot
Disallow: /
User-agent: ZyBORG
Disallow: /
User-agent: AdsBot-Google
Allow: /
User-agent: Mediapartners-Google
Allow: /
User-agent: Googlebot
Allow: /Special:NewPages
Allow: /Special:Sitemap
Allow: /Special:CategoryListing
Allow: /
Disallow: /wikiHowTo
User-agent: *
Allow: /Special:Block
Allow: /Special:BlockList
Allow: /Special:Categorylisting
Allow: /Special:CategoryListing
Allow: /Special:Charity
Allow: /Special:EmailUser
Allow: /Special:LSearch
Allow: /Special:NewPages
Allow: /Special:QABox
Allow: /Special:SearchAd
Allow: /Special:Sitemap
Allow: /Special:ThankAuthors
Allow: /Special:UserLogin
Allow: /index.php?*action=credits
Allow: /index.php?*MathShowImage
Allow: /index.php?*printable
Disallow: /index.php
Disallow: /*feed=rss
Disallow: /*action=delete
Disallow: /*action=history
Disallow: /Special:
Disallow: /*platform=
Disallow: /*variant=
Disallow: /wikiHowTo
CTLS Certificate Expiry & RecommendationsAction21 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Renew certificate — 21 days remaining
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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 Records4 A records, 31 ms lookupPASS
| A | 151.101.65.91, 151.101.129.91, 151.101.193.91, 151.101.1.91 |
| AAAA | — |
| CNAME | — |
| NS | ns13.dnsmadeeasy.com, ns10.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns15.dnsmadeeasy.com |
| MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 aspmx2.googlemail.com 40 aspmx3.googlemail.com |
| TXT | google-site-verification=43MefOk7LUscgOGFrpDNu6YFwFUREjZq1AnRNr-Z4E0 _globalsign-domain-verification=l_BNpBAnk-rKZRyXJ9UkBfv9o6EEuuenkBrGpYNYo0 SPF v=spf1 include:sendgrid.net include:_spf.google.com include:servers.mcsv.net inc... brave-ledger-verification=1def9d4701e2cee252a492ad5cf060aa6663a2f6deba6298dd326e... google-site-verification=xWNUj_2Mfx3WiSM9x5Oib0eG_tiORZ136-jxVyibXmE openai-domain-verification=dv-QeGaIlIxGTi3MGFKmW25W9hy |
| 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.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencewikihow.com — via Network Solutions, LLC, 22 years, 2 months old, hosted on FastlyPASS
2525 days
June 12, 2033
21 days
Issued by Certainly
22 years, 2 months
Registered June 12, 2004
Not enabled
Protects against DNS spoofing
Fastly
ASN AS54113
151.101.65.91
Network Solutions, LLC
Expiry timeline
Recommended actions
- Renew the TLS certificate or verify auto-renewal is working
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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