Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CCrawlabilityActionrobots.txt present, sitemap with 135 URLsREVIEW
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
# https://www.robotstxt.org/robotstxt.html
User-agent: CCBot
Disallow: /
User-agent: img2dataset
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: Omgilibot
Disallow: /
User-agent: Omgili
Disallow: /
User-agent: FacebookBot
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: magpie-crawler
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: Perplexity‑User
Disallow: /
# General rules for all other bots
User-agent: *
# Place allows first to avoid bots skipping after Disallow: /
# Allow exactly the homepage
Allow: /$
# Allow the homepage with any query parameters
Allow: /?*
Allow: /api/share/og/
Allow: /g/
Allow: /s/
Allow: /gg/v/
Allow: /share/
Allow: /canvas/shared/
Allow: /*/images
Allow: /images
Allow: /*/library
Allow: /library
Allow: /favicon.ico
Allow: /assets/favicon
Allow: /cdn/assets/favicon
Allow: /auth/
Allow: /gpts$
Allow: /codex$
Allow: /codex/$
Allow: /search$
Allow: /backend-anon/
Allow: /public-api/
Allow: /sitemap.xml
Allow: /marketing-sitemap.xml
Allow: /100chats
Allow: /api/public_content/
Allow: /backend-api/public_content/
Allow: /?ref=dotcom
# Static Landing Pages
Allow: /overview
Allow: /*/overview
Allow: /features
Allow: /*/features
Allow: /apps
Allow: /*/apps
Allow: /shopping
Allow: /*/shopping
Allow: /use-cases
Allow: /*/use-cases
Allow: /learn
Allow: /*/learn
Allow: /business
Allow: /*/business
Allow: /pricing
Allow: /*/pricing
Allow: /download
Allow: /*/download
Allow: /students
Allow: /*/college-students
Allow: /college-students
Allow: /contact-sales
Allow: /*/contact-sales
Allow: /100chats-project
Allow: /*/100chats-project
Allow: /merchants
Allow: /*/merchants
Allow: /parent-resources
Allow: /*/parent-resources
Allow: /atlas
Allow: /*/atlas
Allow: /plans
Allow: /*/plans
Allow: /translate
Allow: /*/translate
Allow: /chatgpt-26
Allow: /*/chatgpt-26
Allow: /codex/get-started/$
Allow: /*/codex/get-started/$
Allow: /codex/students
Allow: /*/codex/students
# Exact locale specific homepages
Allow: /am/$
Allow: /ar/$
Allow: /bg-BG/$
Allow: /bn-BD/$
Allow: /bs-BA/$
Allow: /ca-ES/$
Allow: /cs-CZ/$
Allow: /da-DK/$
Allow: /de-DE/$
Allow: /el-GR/$
Allow: /es-ES/$
Allow: /es-419/$
Allow: /et-EE/$
Allow: /fi-FI/$
Allow: /fr-FR/$
Allow: /fr-CA/$
Allow: /gu-IN/$
Allow: /hi-IN/$
Allow: /hr-HR/$
Allow: /hu-HU/$
Allow: /hy-AM/$
Allow: /id-ID/$
Allow: /is-IS/$
Allow: /it-IT/$
Allow: /ja-JP/$
Allow: /ka-GE/$
Allow: /kk/$
Allow: /kn-IN/$
Allow: /ko-KR/$
Allow: /lt/$
Allow: /lv-LV/$
Allow: /mk-MK/$
Allow: /ml/$
Allow: /mn/$
Allow: /mr-IN/$
Allow: /ms-MY/$
Allow: /my-MM/$
Allow: /nb-NO/$
Allow: /nl-NL/$
Allow: /pa/$
Allow: /pl-PL/$
Allow: /pt-BR/$
Allow: /pt-PT/$
Allow: /ro-RO/$
Allow: /ru-RU/$
Allow: /sk-SK/$
Allow: /sl-SI/$
Allow: /so-SO/$
Allow: /sq-AL/$
Allow: /sr-RS/$
Allow: /sv-SE/$
Allow: /sw-TZ/$
Allow: /ta-IN/$
Allow: /te-IN/$
Allow: /th-TH/$
Allow: /tl/$
Allow: /tr-TR/$
Allow: /uk-UA/$
Allow: /ur/$
Allow: /vi-VN/$
Allow: /zh-CN/$
Allow: /zh-TW/$
Allow: /zh-HK/$
# Now block everything else
Disallow: /
# Specific disallows (redundant for some bots, but still useful for those that respect precedence)
Disallow: /auth/logout
Disallow: /auth/login?*
Disallow: /backend-anon/sentinel/*
Disallow: /backend-anon/conversation$
Disallow: /account-link/*
Sitemap: https://chatgpt.com/sitemap.xml
Sitemap: https://chatgpt.com/marketing-sitemap.xml
BTLS Certificate Expiry & Recommendations65 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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 Records2 A records, 15 ms lookupPASS
| A | 104.18.32.47, 172.64.155.209 |
| AAAA | 2a06:98c1:3100::6812:202f, 2a06:98c1:310b::ac40:9bd1 |
| CNAME | — |
| NS | hassan.ns.cloudflare.com, savanna.ns.cloudflare.com |
| MX | — |
| TXT | google-site-verification=3p_zWfTXlQ4Mbxvq51ylW59LjgneYCB_vXpS-DLIEwM google-site-verification=qz8yKZH1f2h4Dl7S-nRAo0immoInmiosRhyjUxXuUOs google-site-verification=rZodbEw8Hlw3gg7Z7mxkmQUNPnO_1khlohRX5D6qeUo google-site-verification=u3JFUrrlvyiaVlGsdIRMgmuvDluR6gC-TIPBEQLbl8c google-site-verification=vHr-4wFDXLd3wze6i0YimpiGHC1u0Hy3x1dGAiyeHWs SPF v=spf1 -all |
| 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+Redirect ChainNo redirects — direct accessPASS
https://chatgpt.com
135 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://chatgpt.com | 200 | 135 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencechatgpt.com — via MarkMonitor Inc., 3 years, 5 months oldPASS
141 days
November 30, 2026
65 days
Issued by Google Trust Services
3 years, 5 months
Registered November 30, 2022
Not enabled
Protects against DNS spoofing
Unknown
2a06:98c1:310b::ac40:9bd1
MarkMonitor 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