Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1147 ms totalFIX
https://nyc.gov
672 ms · HTTP/1.1
https://www.nyc.gov/
162 ms · HTTP/1.1
https://www.nyc.gov/main
313 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://nyc.gov | 301 | 672 ms | HTTP/1.1 | |
| 2 | https://www.nyc.gov/ | 301 | 162 ms | HTTP/1.1 | |
| 3 | https://www.nyc.gov/main | 200 | 313 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
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
BTLS Certificate Expiry & Recommendations321 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records1 A records, 131 ms lookupPASS
| A | 157.188.15.121 |
| AAAA | — |
| CNAME | — |
| NS | ns1.nyc.gov, ns2.nyc.gov, ns3.nyc.gov, ns4.nyc.gov |
| MX | 10 mxa-004c8901.gslb.pphosted.com 10 mxb-004c8901.gslb.pphosted.com |
| TXT | docusign=1f5c2abb-6841-4b96-9d78-1aadc40c4821 knowbe4-site-verification=e24c5649362beaa450442c7abb0e60b6 SPF v=spf1 include:_spf.nyc.gov include:spf-004c8901.pphosted.com -all google-site-verification=BBU-ICoG06y5Xtw4YVtzP8tA8Q-qEY_taVu2p53OcvI google-site-verification=bI6ZtsUeCxEGSTMgRwDa2Gqkh0LKV5G2j25IMbV8m9M google-site-verification=c2rxSkeOeLiHnbcn-IxYfnfB2Pq43SyixEdki686e44 google-site-verification=hEsSjO7qQCEGsZICrCP_c18pUY6D1XbBt3FAXdO7fDA dell-technologies-domain-verification=oti.nyc.gov_c194afe4-4c1b-4cc1-a072-7f6f73... |
| 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.
A+Crawlabilityrobots.txt present, sitemap with 4 URLsPASS
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: *
Disallow: /html/misc/
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencenyc.gov — via get.gov, 28 years, 11 months old, hosted on AS22252 - The City of New York, USPASS
57 days
August 11, 2026
321 days
Issued by DigiCert Inc
28 years, 11 months
Registered October 2, 1997
Enabled
Protects against DNS spoofing
AS22252 - The City of New York, US
ASN AS22252
157.188.15.121
get.gov
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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