Infrastructure - https://sblob.it BeaverCheck Audit

D

CDN & Delivery

Action

No CDN (document or assets)

FIX

No CDN (document or assets)

Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

Got: document origin: OVH

No CDN (document or assets)

Document origin OVH

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

B

DNS Records

1 A records, 568 ms lookup

REVIEW

1 A records, 568 ms lookup

Resolves to 1 IPv4 address(es)

Got: 54.38.205.20

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: dns4.arubadns.cz, dns3.arubadns.net, dns2.technorail.com, dns.technorail.com

1 mail exchanger(s) configured

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution is slow (568 ms)

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

Got: 568 ms

A	54.38.205.20
AAAA	—
CNAME	—
NS	dns4.arubadns.cz, dns3.arubadns.net, dns2.technorail.com, dns.technorail.com
MX	20 mail.sblob.it
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 568 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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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)

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

PTR for 54.38.205.20 does not match any cert SAN: ip20.ip-54-38-205.eu

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

Multi-Resolver DNS Speed

Action

Mean 267ms across 3 resolvers (spread 225ms)

REVIEW

Mean 267ms across 3 resolvers (spread 225ms)

Cloudflare: 176ms

Got: 176ms via 1.1.1.1:53

Google: 225ms

Got: 225ms via 8.8.8.8:53

Quad9: 401ms

Got: 401ms via 9.9.9.9:53

High latency spread between resolvers: 225ms (min 176ms / max 401ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

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

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.sblob.it/

200https://sblob.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://sblob.it/ → https://sblob.it/

Consistent

B

HTTP Probe Timing

Total 1046 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

365 ms

TCP Connect

221 ms

TLS Handshake

228 ms

Time to First Byte

1.05 s

Total Time

1.05 s

Connection waterfall

DNS Lookup 365 ms TCP Connect 221 ms TLS Handshake 228 ms Server Processing 231 ms Content Transfer 1 ms

B

TLS Certificate Expiry & Recommendations

59 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

59

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

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

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.

B

Health Check Endpoint

No conventional health endpoint found

REVIEW

No conventional health endpoint found

Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://sblob.it

https://sblob.it

1201 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://sblob.it	200	1201 ms	HTTP/1.1	Apache

A+

Domain Intelligence

sblob.it — via ARUBA-REG, 4 years, 9 months old, hosted on OVH

PASS

sblob.it — via ARUBA-REG, 4 years, 9 months old, hosted on OVH

Domain registered until Jan 25, 2027 (3 months remaining)

Registrar: ARUBA-REG

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.

Hosting: OVH

Got: AS16276

Domain expiry

113 days

January 25, 2027

SSL certificate

59 days

Issued by Let's Encrypt

Domain age

4 years, 9 months

Registered January 25, 2022

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

54.38.205.20

Registrar

ARUBA-REG

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar ARUBA-REG

Created January 25, 2022 (4 years, 9 months ago)

Expires January 25, 2027 (3 months)

Last Updated February 10, 2026

Name Servers dns.technorail.com, dns2.technorail.com, dns3.arubadns.net, dns4.arubadns.cz

Registrant DIFNET SRLS

Hosting

IP Address 54.38.205.20

ASN AS16276 (OVH - OVH SAS, FR)

Provider OVH

Data source: whois (1.4s)

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