Skip to content
https://art.pl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
3 PASS 5 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
Redirect Chain
1 redirect(s), 1852 ms total
REVIEW
1 redirect(s), 1852 ms total
Info::
Single redirect
Got: https://art.pl → https://domeny.art.pl/ (301)
Warning::
Redirect overhead: 1852 ms total
Got: 1852 ms
Info::
Cross-domain redirect detected

https://art.pl

887 ms · HTTP/1.1

301

https://domeny.art.pl/

965 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://art.pl301887 msHTTP/1.1nginx
2https://domeny.art.pl/200965 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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: 23 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 23 B Sitemaps referenced 0 User-agents * 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 875 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
211 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
220 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
223 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
875 ms
Total Time Total request time from DNS lookup through full response.
875 ms

Connection waterfall

DNS Lookup 211 ms TCP Connect 220 ms TLS Handshake 223 ms Server Processing 221 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
37 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

37
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
A
DNS Records
1 A records, 628 ms lookup
PASS
1 A records, 628 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 146.59.33.164
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: ns14.ovh.net, dns14.ovh.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (628 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 628 ms
A146.59.33.164
AAAA
CNAME
NSns14.ovh.net, dns14.ovh.net
MX
5 mail.net.icm.edu.pl
TXT
SPF v=spf1 a mx include:_spf.mlsend.com ~all
mailerlite-domain-verification=736dca2e3e49b11e2f02f8851269eca98f01d60c
CAALookup not available with standard resolver
Resolved in 628 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

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.

Why this matters

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

Source: DNS performance benchmarks

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 301-redirects to HTTPS

www / non-www

301https://www.art.pl/
200https://art.pl/

Preferred variant: non-www

HTTP → HTTPS

301http://art.pl/ https://art.pl/

Consistent

A+
Domain Intelligence
art.pl — via Consulting Service Sp. z o.o., 31 years, 9 months old, hosted on OVH
PASS
art.pl — via Consulting Service Sp. z o.o., 31 years, 9 months old, hosted on OVH
Info::
Domain registered until Dec 31, 2032 (6 years, 9 months 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: Consulting Service Sp. z o.o.
Info::
Hosting: OVH
Got: AS16276
Domain expiry

2360 days

December 31, 2032

SSL certificate

37 days

Issued by Let's Encrypt

Domain age

31 years, 9 months

Registered January 1, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

146.59.33.164

Registrar

Consulting Service Sp. z o.o.

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 Consulting Service Sp. z o.o.
Created January 1, 1995 (31 years, 9 months ago)
Expires December 31, 2032 (6 years, 9 months)
Last Updated May 10, 2022
Name Servers ns14.ovh.net, dns14.ovh.net
DNSSEC Not enabled
Hosting
IP Address 146.59.33.164
ASN AS16276 (OVH, FR)
Provider OVH
Data source: rdap (1.2s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback