Skip to content
https://koloseum.com.pl

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
6 PASS 10 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 188.210.220.241 does not match any cert SAN: mail.koloseum.gda.pl
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Multi-Resolver DNS Speed
Mean 172ms across 3 resolvers (spread 17ms)
REVIEW
Mean 172ms across 3 resolvers (spread 17ms)
Info::
Quad9: 165ms
Got: 165ms via 9.9.9.9:53
Info::
Cloudflare: 171ms
Got: 171ms via 1.1.1.1:53
Info::
Google: 182ms
Got: 182ms via 8.8.8.8:53
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 21 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 21 B Sitemaps referenced 0 User-agents *Allow: / Blocking No — crawling allowed
User-agent: *Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 893 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
339 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
167 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
172 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
893 ms
Total Time Total request time from DNS lookup through full response.
894 ms

Connection waterfall

DNS Lookup 339 ms TCP Connect 167 ms TLS Handshake 172 ms Server Processing 215 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
85 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

85
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A
DNS Records
1 A records, 347 ms lookup
PASS
1 A records, 347 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 188.210.220.241
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.seohost.pl, ns2.seohost.pl
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (347 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 347 ms
A188.210.220.241
AAAA—
CNAME—
NSns1.seohost.pl, ns2.seohost.pl
MX
0 koloseum-com-pl.mail.protection.outlook.com
TXT
MS=ms20143726
SPF v=spf1 include:spf.protection.outlook.com include:_spf.emaillabs.net.pl -all
CAALookup not available with standard resolver
Resolved in 347 ms

Multiple A records provide failover if one server goes down.

Why this matters

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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://koloseum.com.pl

https://koloseum.com.pl

858 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://koloseum.com.pl200858 msHTTP/1.1LiteSpeed
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.koloseum.com.pl/
200https://koloseum.com.pl/

Preferred variant: non-www

HTTP → HTTPS

301http://koloseum.com.pl/ → https://koloseum.com.pl/

Consistent

A+
Domain Intelligence
koloseum.com.pl — via PERSKIMEDIA Szymon Perski, 3 years old, hosted on DATASPACE - DATASPACE P.S.A., PL
PASS
koloseum.com.pl — via PERSKIMEDIA Szymon Perski, 3 years old, hosted on DATASPACE - DATASPACE P.S.A., PL
Info::
Domain registered until Sep 14, 2027 (1 years remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: PERSKIMEDIA Szymon Perski
Info::
Hosting: DATASPACE - DATASPACE P.S.A., PL
Got: AS50599
Domain expiry

379 days

September 14, 2027

SSL certificate

85 days

Issued by Let's Encrypt

Domain age

3 years

Registered September 14, 2023

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DATASPACE - DATASPACE P.S.A., PL

ASN AS50599

188.210.220.241

Registrar

PERSKIMEDIA Szymon Perski

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar PERSKIMEDIA Szymon Perski
Created September 14, 2023 (3 years ago)
Expires September 14, 2027 (1 years)
Last Updated August 31, 2026
Name Servers ns1.seohost.pl, ns2.seohost.pl
DNSSEC Not enabled
Hosting
IP Address 188.210.220.241
ASN AS50599 (DATASPACE - DATASPACE P.S.A., PL)
Provider DATASPACE - DATASPACE P.S.A., PL
Data source: rdap (0.8s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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

A+
Health Check Endpoint
Health endpoint at https://koloseum.com.pl/api/health (HTTP 200)
PASS
Health endpoint at https://koloseum.com.pl/api/health (HTTP 200)
Info::
Public health endpoint at https://koloseum.com.pl/api/health
Got: https://koloseum.com.pl/api/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback