Skip to content
https://golink.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.golink.it/
200https://golink.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://golink.it/

HTTP version does not redirect to HTTPS

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 192.250.229.216 does not match any cert SAN: s4474.fra1.stableserver.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
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 44 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 44 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /service/

Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
79 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

79
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
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, 57 ms lookup
PASS
1 A records, 57 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.250.229.216
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: ns1.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com, ns2.mysecurecloudhost.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 57 ms
Got: 57 ms
A192.250.229.216
AAAA—
CNAME—
NSns1.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com, ns2.mysecurecloudhost.com
MX
0 mail.golink.it
TXT
SPF v=spf1 ip4:192.250.229.216 include:spf.mysecurecloudhost.com ip4:191.96.52.4 +a ...
CAALookup not available with standard resolver
Resolved in 57 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 42ms across 3 resolvers (spread 28ms)
PASS
Mean 42ms across 3 resolvers (spread 28ms)
Info::
Cloudflare: 26ms
Got: 26ms via 1.1.1.1:53
Info::
Quad9: 46ms
Got: 46ms via 9.9.9.9:53
Info::
Google: 54ms
Got: 54ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://golink.it

https://golink.it

88 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://golink.it20088 msHTTP/1.1LiteSpeed
A+
Domain Intelligence
golink.it — via GIDINET-REG, 25 years, 4 months old, hosted on WHG-FRA - WHG Hosting Services Ltd, GB
PASS
golink.it — via GIDINET-REG, 25 years, 4 months old, hosted on WHG-FRA - WHG Hosting Services Ltd, GB
Info::
Domain registered until Dec 19, 2026 (5 months remaining)
Info::
Registrar: GIDINET-REG
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: WHG-FRA - WHG Hosting Services Ltd, GB
Got: AS209341
Domain expiry

158 days

December 19, 2026

SSL certificate

79 days

Issued by Let's Encrypt

Domain age

25 years, 4 months

Registered July 17, 2001

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

WHG-FRA - WHG Hosting Services Ltd, GB

ASN AS209341

192.250.229.216

Registrar

GIDINET-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 GIDINET-REG
Created July 17, 2001 (25 years, 4 months ago)
Expires December 19, 2026 (5 months)
Last Updated January 4, 2026
Name Servers ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com
Registrant Giuseppe Caporale
Hosting
IP Address 192.250.229.216
ASN AS209341 (WHG-FRA - WHG Hosting Services Ltd, GB)
Provider WHG-FRA - WHG Hosting Services Ltd, GB
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

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

Connection waterfall

DNS Lookup 55 ms TCP Connect 28 ms TLS Handshake 30 ms Server Processing 34 ms Content Transfer 1 ms
A+
Health Check Endpoint
Health endpoint at https://golink.it/health (HTTP 200)
PASS
Health endpoint at https://golink.it/health (HTTP 200)
Info::
Public health endpoint at https://golink.it/health
Got: https://golink.it/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback