Skip to content
https://ladysilvia.eu

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 9 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 62.141.52.97 does not match any cert SAN: km20615-02.keymachine.de
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.
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.ladysilvia.eu/
200https://ladysilvia.eu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ladysilvia.eu/ → https://lsnn.net/

Consistent

B
HTTP Probe Timing
Total 867 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
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.
33 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
70 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
865 ms
Total Time Total request time from DNS lookup through full response.
868 ms

Connection waterfall

DNS Lookup 69 ms TCP Connect 33 ms TLS Handshake 70 ms Server Processing 692 ms Content Transfer 2 ms
B
TLS Certificate Expiry & Recommendations
80 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 91 ms lookup
PASS
1 A records, 91 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 62.141.52.97
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns4.arubadns.cz, dns.technorail.com, dns2.technorail.com, dns3.arubadns.net
Info::
No MX records — email not configured via DNS
Info::
SPF record present in TXT
Info::
DNS resolution time: 91 ms
Got: 91 ms
A62.141.52.97
AAAA—
CNAME—
NSdns4.arubadns.cz, dns.technorail.com, dns2.technorail.com, dns3.arubadns.net
MX—
TXT
SPF v=spf1 ip4:66.96.128.0/18 ?all
CAALookup not available with standard resolver
Resolved in 91 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Multi-Resolver DNS Speed
Mean 55ms across 3 resolvers (spread 25ms)
PASS
Mean 55ms across 3 resolvers (spread 25ms)
Info::
Quad9: 46ms
Got: 46ms via 9.9.9.9:53
Info::
Google: 50ms
Got: 50ms via 8.8.8.8:53
Info::
Cloudflare: 71ms
Got: 71ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://ladysilvia.eu

https://ladysilvia.eu

182 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ladysilvia.eu200182 msHTTP/1.1Apache/2.4.6 (CentOS) PHP/8.3.2 OpenSSL/1.0.2k-fips
A+
Crawlability
robots.txt present, sitemap with 2001 URLs
PASS
robots.txt present, sitemap with 2001 URLs
Info::
robots.txt is present
Got: 3131 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2001 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3131 B Sitemaps referenced 5 User-agents Googlebot, Discordbot, feedreader, facebookexternalhit, Telegrambot, Inoreader, *, AmazonBot, MJ12bot, WhatsApp, Slack-ImgProxy, Ahrefs, DotBot, SemrushBot-BA, Flipboard, bingbot, Baidu, DuckDuckGo, Feedly, Pocketbot, Amazonbot, SemrushBot, AhrefsSiteAudit, Slurp, Googlebot-News, Twitterbot, AhrefsBot, YandexBot, LinkedInBot Blocking No — crawling allowed
# robots.txt - Multi-brand friendly with SEO Tool Blocking

# =====================================================
# BLOCK SEO Tools & Competitors (Bandwidth Savers)
# =====================================================
User-agent: Amazonbot
Disallow: /

User-agent: AmazonBot
Disallow: /

User-agent: Ahrefs
Disallow: /

User-agent: SemrushBot
Disallow: /

User-agent: MJ12bot
Disallow: /

User-agent: AhrefsBot
Disallow: /

User-agent: DotBot
Disallow: /

User-agent: SemrushBot-BA
Disallow: /

User-agent: AhrefsSiteAudit
Disallow: /

# =====================================================
# Google News Crawlers (ALLOW)
# =====================================================
User-agent: Googlebot-News
Allow: /

User-agent: Googlebot
Allow: /

# =====================================================
# Search Engines (ALLOW)
# =====================================================
User-agent: bingbot
Allow: /

User-agent: Slurp
Allow: /

User-agent: Baidu
Allow: /

User-agent: YandexBot
Allow: /

User-agent: DuckDuckGo
Allow: /

# =====================================================
# Social Media & Feed Crawlers (ALLOW)
# =====================================================
User-agent: facebookexternalhit
Allow: /

User-agent: Twitterbot
Allow: /

User-agent: LinkedInBot
Allow: /

User-agent: WhatsApp
Allow: /

User-agent: Telegrambot
Allow: /

User-agent: Slack-ImgProxy
Allow: /

User-agent: Discordbot
Allow: /

# =====================================================
# Feed Readers (ALLOW)
# =====================================================
User-agent: feedreader
Allow: /

User-agent: Feedly
Allow: /

User-agent: Inoreader
Allow: /

User-agent: Flipboard
Allow: /

User-agent: Pocketbot
Allow: /

# =====================================================
# Standard Crawlers (Default: CONTROLLED ACCESS)
# =====================================================
User-agent: *
Allow: /

Disallow: /admin/
Disallow: /api/
Disallow: /test/
Disallow: /tmp/
Disallow: /cache/
Disallow: /.git/
Disallow: /.env
Disallow: /node_modules/
Disallow: /vendor/
Disallow: /config/
Disallow: *?sort=
Disallow: *?page=
Disallow: */search?
Disallow: */filter?
Disallow: */edit
Disallow: */delete

# Crawl Policy
Crawl-delay: 2
Request-rate: 30/60

# =====================================================
# Sitemaps (Multi-brand - STATIC FILES)
# =====================================================
# Ladysilvia
Sitemap: https://ladysilvia.com/sitemap.xml
Sitemap: https://ladysilvia.eu/sitemap.xml

# Flashsport
Sitemap: https://flashsport.space/sitemap.xml

# Planetjournal (gaia)
Sitemap: https://www.planetjournal.online/sitemap.xml

# Rockitalia
Sitemap: https://rockitalia.net/sitemap.xml

# =====================================================
# Feed URLs (Optional for Crawlers)
# =====================================================
# Ladysilvia Feed: https://ladysilvia.eu/static/feed.php?brand=ladysilvia&format=rss
# Flashsport Feed: https://flashsport.space/static/feed.php?brand=flashsport&format=rss
# Planetjournal Feed: https://www.planetjournal.online/static/feed.php?brand=planetjournal&format=rss
sitemap.xml 200 OK
Type URL Set URLs 2001 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
ladysilvia.eu — via Aruba S.p.A., hosted on KEYWEB-AS - Keyweb AG, DE
PASS
ladysilvia.eu — via Aruba S.p.A., hosted on KEYWEB-AS - Keyweb AG, DE
Info::
Registrar: Aruba S.p.A.
Info::
Hosting: KEYWEB-AS - Keyweb AG, DE
Got: AS31103
Domain expiry

Unknown

SSL certificate

80 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

KEYWEB-AS - Keyweb AG, DE

ASN AS31103

62.141.52.97

Registrar

Aruba S.p.A.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar Aruba S.p.A.
Name Servers dns3.arubadns.net, dns2.technorail.com, dns4.arubadns.cz, dns.technorail.com
Registrant NOT DISCLOSED!
Hosting
IP Address 62.141.52.97
ASN AS31103 (KEYWEB-AS - Keyweb AG, DE)
Provider KEYWEB-AS - Keyweb AG, DE
Data source: whois (0.9s)
A+
Health Check Endpoint
Health endpoint at https://ladysilvia.eu/health (HTTP 200)
PASS
Health endpoint at https://ladysilvia.eu/health (HTTP 200)
Info::
Public health endpoint at https://ladysilvia.eu/health
Got: https://ladysilvia.eu/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback