Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CCrawlabilityActionrobots.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
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
# robots.txt for http://www.newyorkfed.org/
User-agent: *
Disallow: /PrincipleInterest/
Disallow: /research/economists/RSG_SeminarsCalendar.pdf
Disallow: /research/economists/RSG_VisitorsCalendar.pdf
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations63 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
BCDN & DeliveryAkamaiREVIEW
A+DNS Records2 A records, 29 ms lookupPASS
| A | 2.16.245.157, 2.16.245.173 |
| AAAA | 2a02:26f0:1180:35::210:6ad8, 2a02:26f0:1180:35::210:6ad5 |
| CNAME | — |
| NS | pdns108.ultradns.net, ns60.ultradns2.org, ns60.ultradns2.com, pdns108.ultradns.biz, pdns108.ultradns.org, pdns108.ultradns.com |
| MX | 10 mx1.frb.iphmx.com 10 mx2.frb.iphmx.com |
| TXT | _tn7cjb90aysrmmw90cov48cqvryfqeg _siaicaa2frdiq9vlj7sc1qw93fszav6 9J4Uo5ejJr1NjaHbJ4UEyzTO6yw:DBCC-F785-73CC-3D17-CDC3-5DA7-1D66-A75F SPF v=spf1 ip4:199.169.200.4 ip4:199.169.204.4 ip4:199.169.240.69 ip4:199.169.208.69... yr2tccylxlnb7n3myh47zxcj6vhmv0gw MS=ms51797334 _38lh84f5t8usuwricys5cc0obj3afmi 0mzjnghjsggbnzrf74cv90q8y4y7d5yy c2k059lmnshllwdzx8nmbypmqlw31t4k CS0008430 CS0008431 |
| 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), 298 ms totalPASS
https://newyorkfed.org
82 ms · HTTP/1.1
https://www.newyorkfed.org/
216 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://newyorkfed.org | 301 | 82 ms | HTTP/1.1 | AkamaiGHost |
| 2 | https://www.newyorkfed.org/ | 200 | 216 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (30 ms)PASS
A+Domain Intelligencenewyorkfed.org — via GoDaddy.com, LLC, 26 years, 10 months oldPASS
132 days
October 26, 2026
63 days
Issued by Let's Encrypt
26 years, 10 months
Registered October 26, 1999
Not enabled
Protects against DNS spoofing
Unknown
2a02:26f0:1180:35::210:6ad5
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