Skip to content
https://euobserver.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
9
6 PASS 2 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.

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
TLS Certificate Expiry & Recommendations
66 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

66
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
2 A records, 227 ms lookup
PASS
2 A records, 227 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 92.60.51.22, 92.60.51.23
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns1.websupport.sk, ns2.websupport.sk, ns3.websupport.sk
Info::
5 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 (227 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 227 ms
A92.60.51.22, 92.60.51.23
AAAA
CNAME
NSns1.websupport.sk, ns2.websupport.sk, ns3.websupport.sk
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=-4xwBh2CHo255TKcJHD2NA76T_dEb9JpqCvJZjU8zLg
google-site-verification=nCuOlCsdv5sMtb31K3NtnR5hY5FxVJgm--6VMlYdA0g
SPF v=spf1 include:_spf.google.com include:servers.mcsv.net include:amazonses.com ~a...
CAALookup not available with standard resolver
Resolved in 227 ms

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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://euobserver.com

https://euobserver.com

694 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://euobserver.com200694 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 307 URLs
PASS
robots.txt present, sitemap with 307 URLs
Info::
robots.txt is present
Got: 608 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 307 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 608 B Sitemaps referenced 2 User-agents CCBot, Google-Extended, GPTBot, omgili, anthropic-ai, Claude-Web, *, Bytespider, Diffbot, FacebookBot, ClaudeBot, cohere-ai, msnbot, PetalBot Blocking No — crawling allowed
User-agent: *
Sitemap: https://euobserver.com/sitemap-news.xml
Sitemap: https://euobserver.com/sitemap-index.xml

User-agent: *
Disallow: *preview=true*

User-agent: msnbot
Crawl-delay: 1

User-agent: PetalBot
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: omgili
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: cohere-ai
Disallow: /

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.euobserver.com/
200https://euobserver.com/

Preferred variant: non-www

HTTP → HTTPS

301http://euobserver.com/ https://euobserver.com/

Consistent

A+
Domain Intelligence
euobserver.com — via Gransy, s.r.o., 26 years, 6 months old, hosted on BONET UPSTREAM, SK
PASS
euobserver.com — via Gransy, s.r.o., 26 years, 6 months old, hosted on BONET UPSTREAM, SK
Info::
Domain registered until Mar 6, 2028 (1 years, 10 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: Gransy, s.r.o.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: BONET UPSTREAM, SK
Got: AS44185
Domain expiry

602 days

March 6, 2028

SSL certificate

66 days

Issued by Let's Encrypt

Domain age

26 years, 6 months

Registered March 6, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

BONET UPSTREAM, SK

ASN AS44185

92.60.51.23

Registrar

Gransy, s.r.o.

Unlocked 3 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Gransy, s.r.o.
Created March 6, 2000 (26 years, 6 months ago)
Expires March 6, 2028 (1 years, 10 months)
Last Updated March 11, 2026
Name Servers ns1.websupport.sk, ns2.websupport.sk, ns3.websupport.sk
DNSSEC Not enabled
Hosting
IP Address 92.60.51.23
ASN AS44185 (BONET UPSTREAM, SK)
Provider BONET UPSTREAM, SK
Data source: rdap (0.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

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.

Why this matters

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

A
HTTP Probe Timing
Total 719 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
69 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
161 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
163 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
555 ms
Total Time Total request time from DNS lookup through full response.
720 ms

Connection waterfall

DNS Lookup 69 ms TCP Connect 161 ms TLS Handshake 163 ms Server Processing 162 ms Content Transfer 165 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback