Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, sitemap with 0 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
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
User-agent: LinkedInBot
Allow: */health/*
User-agent: Scope3/2.0 (scope3.com)
Allow: /
User-agent: *
# Directories
Disallow: *?cmt=
Disallow: *?est=
Disallow: *?p=
Disallow: *?af_sub1=
Disallow: *?slsuccess=
Disallow: *?pipa_verify_email=
Disallow: *?pipa_reset_password=
Disallow: *?lwpw=
Disallow: *?welcomeuser=
Disallow: *?rs=
Disallow: *?fbclid=
Disallow: *?mobile=
Disallow: *?__twitter_impression=
Disallow: *?fb_comment_id=
Disallow: *?li_source=
Disallow: *?s=
Disallow: *?sidebar=
Disallow: *?photo=
Disallow: *?v=
Disallow: *?duration=
Disallow: *?src_src=
Disallow: *?welcomeuser=
Disallow: *?ea_med=
Disallow: *?src_cat=
Disallow: *?w3tc_preview=
Disallow: *?sidebar=
Disallow: *?share=
Disallow: *?_gl=
Disallow: *?Wb=
Disallow: *?_page=
Disallow: /*?ea_src=
Disallow: /*?_rsc=
Disallow: /*?amu=
Disallow: /*?gbraid=
Disallow: */uncategorized/*
Disallow: /wp-includes/*
Disallow: /wp-admin/*
Disallow: /wp-content/plugins/*
Disallow: /assets/plugins/*
Disallow: /search/*
Disallow: /feedback/*
Disallow: /*?q=*
Disallow: /*?ref
Disallow: *utm_
User-agent: Twitterbot
Allow: /*?*utm_
User-agent: facebookexternalhit
Allow: /*?*utm_
# AI retrieval crawlers — ALLOW
User-agent: OAI-SearchBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: Google-Extended
Allow: /
# AI training crawlers — BLOCK if desired
User-agent: GPTBot
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-Agent: omgilibot
Disallow: /
User-Agent: omgili
Disallow: /
User-Agent:Mediatoolkitbot
Disallow: /
User-Agent:PolecatBot
Disallow: /
User-Agent:DotBot
Disallow: /
Sitemap: https://www.theepochtimes.com/sitemap/sitemap.xml.gz
Sitemap: https://www.theepochtimes.com/sitemap/sitemap-news.xml.gz
Sitemap: https://www.theepochtimes.com/sitemap/sitemap-allvideos.xml.gz
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations105 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 39 ms lookupPASS
| A | 104.17.157.22, 104.17.158.22 |
| AAAA | 2606:4700::6811:9e16, 2606:4700::6811:9d16 |
| CNAME | — |
| NS | gracie.ns.cloudflare.com, justin.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com |
| TXT | facebook-domain-verification=h8lrrmx4t44h282ti74txsyk0r980n google-site-verification=vvnZaqSO-4SUP2aK9gcD8rLME0UJmwN-CPgf8C1cZHY SPF v=spf1 include:_spf.theepochtimes.com include:spf.youmaker.com include:9200794a.... yandex-verification: bc9b7ecadcdaf23c facebook-domain-verification=cy0qpin6ax3j3x53pjiwyy8wfq5c3w google-site-verification=wY_wcoSOZfSX6a0A905mu9VG8RgaN5T8i4Sy7y44r_Q yahoo-verification-key=U9mkwoISa0UiohRc+nM1sc9AMATYREoUgCtp/c+nAeA= google-site-verification=6Gu0yKq9aOJ1sBUzGkIKuL4ho0WF7piAyO-YmEMeHe0 |
| 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), 185 ms totalPASS
https://theepochtimes.com
63 ms · HTTP/1.1
https://www.theepochtimes.com/
122 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://theepochtimes.com | 301 | 63 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.theepochtimes.com/ | 200 | 122 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (16 ms)PASS
A+Domain Intelligencetheepochtimes.com — via GoDaddy.com, LLC, 22 years, 8 months oldPASS
1645 days
December 17, 2030
105 days
Issued by Sectigo Limited
22 years, 8 months
Registered December 17, 2003
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6811:9e16
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- 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