Infrastructure - https://sevenmore.it BeaverCheck Audit

F

HTTP Probe Timing

Action

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

FIX

DNS Lookup

70 ms

TCP Connect

28 ms

TLS Handshake

33 ms

Time to First Byte

5.19 s

Total Time

5.19 s

Connection waterfall

DNS Lookup 70 ms TCP Connect 28 ms TLS Handshake 33 ms Server Processing 5.06 s Content Transfer 0 ms

D

CDN & Delivery

Action

No CDN detected

FIX

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 (document or assets)

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

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 185.2.4.127 does not match any cert SAN: lhwp1127.webapps.net

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

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

HTTP version does not redirect to HTTPS

Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

507https://www.sevenmore.it/

200https://sevenmore.it/

HTTP → HTTPS

http://sevenmore.it/

HTTP version does not redirect to HTTPS

C

TLS Certificate Expiry & Recommendations

Action

18 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

18

days left

0d 30d 60d 90d+

Renew soon — under 30 days remaining

Recommended actions

Renew certificate — 18 days remaining
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: 429, /health: 429, /healthz: 429, /ping: 429, /status: 429.

A+

DNS Records

1 A records, 52 ms lookup

PASS

1 A records, 52 ms lookup

Resolves to 1 IPv4 address(es)

Got: 185.2.4.127

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: ns1.register.it, ns2.register.it

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 52 ms

Got: 52 ms

A	185.2.4.127
AAAA	—
CNAME	—
NS	ns1.register.it, ns2.register.it
MX	10 mail.register.it
TXT	SPF v=spf1 include:spf.webapps.net ~all
CAA	Lookup not available with standard resolver

Resolved in 52 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 53ms across 3 resolvers (spread 63ms)

PASS

Mean 53ms across 3 resolvers (spread 63ms)

Google: 20ms

Got: 20ms via 8.8.8.8:53

Cloudflare: 56ms

Got: 56ms via 1.1.1.1:53

Quad9: 83ms

Got: 83ms via 9.9.9.9:53

A+

Redirect Chain

No redirect data available

PASS

No redirect data available

No redirect data captured

A+

Domain Intelligence

sevenmore.it — via REGISTER-REG, 9 years, 10 months old, hosted on REGISTER-AS - REGISTER S.P.A., IT

PASS

sevenmore.it — via REGISTER-REG, 9 years, 10 months old, hosted on REGISTER-AS - REGISTER S.P.A., IT

Domain registered until Dec 21, 2026 (3 months remaining)

Registrar: REGISTER-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: REGISTER-AS - REGISTER S.P.A., IT

Got: AS39729

Domain expiry

100 days

December 21, 2026

SSL certificate

18 days

Issued by Let's Encrypt

Domain age

9 years, 10 months

Registered December 21, 2016

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

REGISTER-AS - REGISTER S.P.A., IT

ASN AS39729

185.2.4.127

Registrar

REGISTER-REG

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the TLS certificate or verify auto-renewal is working
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar REGISTER-REG

Created December 21, 2016 (9 years, 10 months ago)

Expires December 21, 2026 (3 months)

Last Updated January 6, 2026

Name Servers ns1.register.it, ns2.register.it

Registrant Michele Romano

Hosting

IP Address 185.2.4.127

ASN AS39729 (REGISTER-AS - REGISTER S.P.A., IT)

Provider REGISTER-AS - REGISTER S.P.A., IT

Data source: whois (1.0s)

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