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.
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
User-Agent: *
Allow: /
BTLS Certificate Expiry & Recommendations253 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
ADNS Records9 A records, 388 ms lookupPASS
| A | 194.181.92.100, 194.181.92.104, 194.181.92.106, 194.181.92.103, 194.181.92.107, 194.181.92.105, 194.181.92.108, 194.181.92.102, 194.181.92.101 |
| AAAA | 2001:a10:e0:3:194:181:92:103, 2001:a10:e0:3:194:181:92:106, 2001:a10:e0:3:194:181:92:102, 2001:a10:e0:3:194:181:92:101, 2001:a10:e0:3:194:181:92:108, 2001:a10:e0:3:194:181:92:104, 2001:a10:e0:3:194:181:92:107, 2001:a10:e0:3:194:181:92:100, 2001:a10:e0:3:194:181:92:105 |
| CNAME | — |
| NS | eomer.nask.net.pl, kirdan.nask.net.pl |
| MX | 10 mx1.www.gov.pl |
| TXT | 1032a2da38dcd15e6c5ac716c171c14a029bfa992747c38b4f7fcb2cd9a11e1 SPF v=spf1 ip4:194.181.92.103 ip4:194.181.92.104 ip4:194.181.92.105 ip4:193.59.100.2... |
| 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.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Redirect ChainNo redirects — direct accessPASS
https://www.gov.pl
392 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.gov.pl | 200 | 392 ms | HTTP/1.1 |
A+IPv6 ReadinessIPv6 reachable (94 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencewww.gov.pl — via NASK, 8 years, 9 months oldPASS
44 days
August 30, 2026
253 days
Issued by Asseco Data Systems S.A.
8 years, 9 months
Registered August 30, 2017
Enabled
Protects against DNS spoofing
Unknown
2001:a10:e0:3:194:181:92:103
NASK
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry