Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FCrawlabilityActionrobots.txt present, sitemap with 0 URLsFIX
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.
Learn more ▾ ▴
Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.
Source: Google Search Central
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
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
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
# Allow important bots
User-agent: googlebot
User-agent: google
User-agent: Mediapartners-Google
User-agent: Google-Display-Ads-Bot
User-agent: bingbot
User-agent: bing
User-agent: facebookexternalhit
User-agent: DuckDuckBot
User-agent: Applebot
Allow: /
# Block specific .php files globally, regardless of their location
User-agent: *
Disallow: */mcp.php
Disallow: */memberlist.php
Disallow: */ucp.php
Disallow: */app.php
Disallow: */viewonline.php
# Set crawl delay to avoid server overload
Crawl-delay: 5
# Block all other unwanted bots
User-agent: *
Disallow: /
DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations45 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records2 A records, 38 ms lookupPASS
| A | 172.66.132.33, 172.66.132.34 |
| AAAA | 2606:4700:10::ac42:8422, 2606:4700:10::ac42:8421 |
| CNAME | — |
| NS | alec.ns.cloudflare.com, gene.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 3 alt2.aspmx.l.google.com 5 aspmx5.googlemail.com 5 alt3.aspmx.l.google.com |
| TXT | SPF v=spf1 ip4:50.19.230.73 ip4:52.232.186.53 ip4:52.179.154.18 ip4:40.84.3.83 ip4:4... google-site-verification=o-jsmKRjU0N9BFz0elixOHZliuqedzXMMnD18vzaC6Y google-site-verification=xj2Kb92dq1lWBfR2afvNT1Jfdw61Mxe5fUwunHJyN6s google-site-verification=j99DSeBTFrrs8VX8-C2kHsw2Y4LXVNNA87Ff81D3HAw |
| 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), 700 ms totalPASS
https://tapatalk.com
465 ms · HTTP/1.1
https://www.tapatalk.com
236 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://tapatalk.com | 301 | 465 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.tapatalk.com | 200 | 236 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Domain Intelligencetapatalk.com — via Cloudflare, Inc., 17 years, 4 months oldPASS
228 days
February 25, 2027
45 days
Issued by Google Trust Services
17 years, 4 months
Registered February 25, 2009
Enabled
Protects against DNS spoofing
Unknown
2606:4700:10::ac42:8421
Cloudflare, Inc.
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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