Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

202 HTTP 202

Checks

6 PASS 10 REVIEW 1 FIX

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: Google

No CDN (document or assets)

Document origin Google

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

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).

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.

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 35.214.159.53 does not match any cert SAN: 53.159.214.35.bc.googleusercontent.com

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.

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

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.

URL Variants

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

REVIEW

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

HTTP version does not redirect to HTTPS

Got: HTTP 202 Expected: 301 redirect to HTTPS

www / non-www

202https://www.weboom.it/

200https://weboom.it/

HTTP → HTTPS

202http://weboom.it/

HTTP version does not redirect to HTTPS

Domain Intelligence

weboom.it — via TUCOWS-REG, 4 years, 11 months old

REVIEW

weboom.it — via TUCOWS-REG, 4 years, 11 months old

Domain expires in 26 days

This domain expires on November 16, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Got: Expires Nov 16, 2026

Registrar: TUCOWS-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.

Domain expiry

26 days

November 16, 2026

SSL certificate

63 days

Issued by Let's Encrypt

Domain age

4 years, 11 months

Registered November 16, 2021

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

ASN AS15169 43515

35.214.159.53

Registrar

TUCOWS-REG

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar TUCOWS-REG

Created November 16, 2021 (4 years, 11 months ago)

Expires November 16, 2026 (26 days)

Last Updated December 2, 2025

Name Servers ns1.siteground.net, ns2.siteground.net

Registrant hidden

Hosting

IP Address 35.214.159.53

ASN AS15169 43515 ()

Data source: whois (0.5s)

This domain expires on November 16, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

TLS Certificate Expiry & Recommendations

63 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

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

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.

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.

A+

DNS Records

1 A records, 58 ms lookup

PASS

1 A records, 58 ms lookup

Resolves to 1 IPv4 address(es)

Got: 35.214.159.53

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns2.siteground.net, ns1.siteground.net

3 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 58 ms

Got: 58 ms

A	35.214.159.53
AAAA	—
CNAME	—
NS	ns2.siteground.net, ns1.siteground.net
MX	10 mx10.antispam.mailspamprotection.com 20 mx20.antispam.mailspamprotection.com 30 mx30.antispam.mailspamprotection.com
TXT	google-site-verification=KyjqN_ZRqbUv96eA14Vf2nVymAjA1lZ4EHpCiRNB1gQ google-site-verification=g3ZkSSU5GLtEvXH-7li8Ndltv9IkFPRZNKb2M8WATZg SPF v=spf1 +a +mx +ip4:35.214.249.40 include:weboom.it.spf.auto.dnssmarthost.net ~a...
CAA	Lookup not available with standard resolver

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

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 39ms across 3 resolvers (spread 16ms)

PASS

Mean 39ms across 3 resolvers (spread 16ms)

Google: 32ms

Got: 32ms via 8.8.8.8:53

Cloudflare: 37ms

Got: 37ms via 1.1.1.1:53

Quad9: 48ms

Got: 48ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://weboom.it

https://weboom.it

119 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://weboom.it	202	119 ms	HTTP/1.1	nginx

A+

HTTP Probe Timing

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

PASS

DNS Lookup

40 ms

TCP Connect

30 ms

TLS Handshake

63 ms

Time to First Byte

248 ms

Total Time

248 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 30 ms TLS Handshake 63 ms Server Processing 115 ms Content Transfer 0 ms

A+

Health Check Endpoint

Health endpoint at https://weboom.it/health (HTTP 202)

PASS

Health endpoint at https://weboom.it/health (HTTP 202)

Public health endpoint at https://weboom.it/health

Got: https://weboom.it/health

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