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.
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations247 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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 Records1 A records, 7 ms lookupPASS
| A | 51.81.5.187 |
| AAAA | — |
| CNAME | — |
| NS | ns11.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns10.dnsmadeeasy.com, ns15.dnsmadeeasy.com, ns12.dnsmadeeasy.com |
| MX | 10 mail.city-data.com |
| TXT | google-site-verification=5q5gU1oLdlTcpuzSo_aNYrf8VTwEdaw6MOhk_eR3SP8 SPF v=spf1 ip4:23.227.169.170 mx include:_spf.google.com -all |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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), 500 ms totalPASS
https://city-data.com
224 ms · HTTP/1.1
https://www.city-data.com/
276 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://city-data.com | 301 | 224 ms | HTTP/1.1 | nginx |
| 2 | https://www.city-data.com/ | 200 | 276 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
ACrawlabilityrobots.txt present, sitemap with 0 URLsPASS
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
User-agent: Mediapartners-Google
Disallow:
User-agent: Mediapartners-Google*
Disallow:
User-agent: msnbot
Crawl-delay: 1
User-agent: *
Disallow: /forum/search.php*
Disallow: /forum/reputation.php*
Disallow: /forum/members
Disallow: /forum/newreply.php*
Disallow: /forum/subscribedforums.php*
Disallow: /cityname.php*
Disallow: /cityname2.php*
Disallow: /news/
Disallow: /blog/?s=
Disallow: /forumc/
Disallow: /forumbeta/
Disallow: /cityw/
Disallow: /roost_ads/
Disallow: /cd_ads/
Disallow: /forum/fort-myers-cape-coral-area/515615-beware-dr-robert-di-fronzo.html
Disallow: /bs/
Disallow: /business-profiles/map.php*
Disallow: /so/*.js
Disallow: /soz/*.js
Disallow: /knowledge/
Disallow: /mapIt.html*
Disallow: /restaurants/afd.class.php*
Disallow: /city/js/getBoxes.php*
Disallow: /county/js/getBoxes.php*
Disallow: /zips/js/getBoxes.php*
Disallow: /neighborhood/js/getBoxes.php*
Disallow: /mtc.class.php*
Disallow: /restaurants/menus/
Disallow: /mod_comments/*
Disallow: /fc/*
User-agent: Google-Extended
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: ImagesiftBot
User-agent: CCBot
User-agent: omgili
User-agent: Diffbot
User-agent: PerplexityBot
User-agent: anthropic-ai
User-agent: FacebookBot
User-agent: PiplBot
User-agent: GPTBot
User-agent: Amazonbot
User-agent: AwarioRssBot
User-agent: AwarioSmartBot
User-agent: cohere-ai
User-agent: DataForSeoBot
User-agent: Webzio-Extended
User-agent: FriendlyCrawler
User-agent: 0AI-SearchBot
User-agent: ImagesiftBot
User-agent: omgili
User-agent: omgilibot
User-agent: PerplexityBot
User-agent: Quora-Bot
User-agent: TurnitinBot
User-agent: Meta-ExternalAgent
User-agent: DataForSeoBot
User-agent: imageSpider
User-agent: ias-ie
User-agent: trendictionbot
User-agent: ias-ie/3.3
Disallow: /
User-agent: 008
Disallow: /
User-agent: sitebot
Disallow: /
User-agent: businessdbbot
Disallow: /
User-agent: magpie-crawle
Disallow: /
User-agent: Bender
Disallow: /
User-agent: MJ12bot
Disallow: /
User-agent: JikeSpider
Disallow: /
User-agent: AhrefsBot
Disallow: /
User-agent: proximic
Disallow: /
User-agent: ADmantX
Disallow: /
User-agent: Mediapartners-Google
Allow: /knowledge
User-agent: Baiduspider
User-agent: 360Spider
User-agent: Yisouspider
User-agent: PetalBot
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: Sogou web spider
Disallow: /
User-agent: Sogou inst spider
Disallow: /
A+Domain Intelligencecity-data.com — via GoDaddy.com, LLC, 22 years, 11 months old, hosted on OVHPASS
432 days
August 22, 2027
247 days
Issued by Sectigo Limited
22 years, 11 months
Registered August 22, 2003
Not enabled
Protects against DNS spoofing
OVH
ASN AS16276
51.81.5.187
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