Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations38 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, 38 ms lookupPASS
| A | 172.66.145.189, 104.20.38.243 |
| AAAA | 2606:4700:10::6814:26f3, 2606:4700:10::ac42:91bd |
| CNAME | — |
| NS | memphis.ns.cloudflare.com, sreeni.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | perplexity-ai-domain-verification-hqm4p5=DPknAfEttZbYiOzO7v0Bx7NBX stripe-verification=04b0f3533f4577bfabe9cff0380b13d9974e056a6077512ec23a51ae99b8... subpage-domain-verification=M3ZHq0A8Jh google-site-verification=xgUX3JaJSo9vfAU2I-q9hEmP64cxvKmngcMJign4DqU brave-ledger-verification=593379c77662e05e93811f1f5e90f28f6a94c5e3cbfbedda1dc20d... SPF v=spf1 include:_spf.google.com include:servers.mcsv.net include:spf.mandrillapp.... tollbit-domain-verification=5e645b8bbbd9ad823dba82b84b7687f551e8ccfe594242f19fa6... BSI102828136040 |
| 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), 168 ms totalPASS
https://worldhistory.org
58 ms · HTTP/1.1
https://www.worldhistory.org/
110 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://worldhistory.org | 301 | 58 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.worldhistory.org/ | 200 | 110 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 10 URLsPASS
# As a condition of accessing this website, you agree to abide by the
# following content signals:
# (a) If a content-signal = yes, you may collect content for the
# corresponding use.
# (b) If a content-signal = no, you may not collect content for the
# corresponding use.
# (c) If the website operator does not include a content signal for a
# corresponding use, the website operator neither grants nor restricts
# permission via content signal with respect to the corresponding use.
# The content signals and their meanings are:
# search: building a search index and providing search results (e.g., returning
# hyperlinks and short excerpts from this website's contents). Search
# does not include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
# augmented generation, grounding, or other real-time taking of
# content for generative AI search answers).
# ai-train: training or fine-tuning AI models.
# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.
# Sitemap
Sitemap: https://www.worldhistory.org/sitemap.xml
# Default Bots
User-agent: *
Content-signal: search=yes, ai-train=no, ai-input=yes
Allow: /
Disallow: /admin/
Disallow: /include/
Disallow: /logout/
Disallow: /moderate/
Disallow: /cdn-cgi/
Disallow: /xres/add/
Disallow: /related/
Disallow: /trans/x/
Disallow: /sponsoranalytics/
Disallow: /analytics/
Allow: /search/$
Disallow: /search/?*
Allow: /map/$
Disallow: /map/*/*
Allow: /interestemails/
Disallow: /interestemails/?*
Disallow: /*/suggested/
# Specific Bots
User-agent: PerplexityBot
User-agent: Perplexity‑User
User-agent: ProRataInc
Content-signal: search=yes, ai-train=yes, ai-input=yes
Allow: /
Disallow: /books/*/
# Advertising Bots
User-agent: AdsBot-Google
User-agent: AmazonAdBot
User-agent: Bidswitchbot
User-agent: CriteoBot
User-agent: DoubleVerifyBot
User-agent: DVBot
User-agent: Grapeshot
User-agent: Gumgum
User-agent: IAS_admantx
User-agent: IAS_crawler
User-agent: IAS_wombles
User-agent: Leikibot
User-agent: Mediapartners-Google
User-agent: Opebot-v
User-agent: Peer39_crawler
User-agent: Proximic
User-agent: PubMatic Crawler Bot
User-agent: SinceraSyntheticUser
User-agent: SlickBot
User-agent: TTD-Content
Allow: /
Disallow: /cf/geoip/
Disallow: /books/*/
- https://www.worldhistory.org/sitemap-1.x...
- https://www.worldhistory.org/sitemap-2.x...
- https://www.worldhistory.org/sitemap-3.x...
- https://www.worldhistory.org/sitemap-4.x...
- https://www.worldhistory.org/sitemap-5.x...
- https://www.worldhistory.org/sitemap-6.x...
- https://www.worldhistory.org/sitemap-7.x...
- https://www.worldhistory.org/sitemap-8.x...
- https://www.worldhistory.org/sitemap-9.x...
- https://www.worldhistory.org/sitemap-10....
A+Domain Intelligenceworldhistory.org — via NameCheap, Inc., 24 years, 4 months oldPASS
1401 days
April 16, 2030
38 days
Issued by Google Trust Services
24 years, 4 months
Registered April 16, 2002
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:10::ac42:91bd
NameCheap, Inc.
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