Skip to content
https://link.space

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
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
TLS Certificate Expiry & Recommendations
52 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

52
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 & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9f087a429f1b0bab-AMS
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f087a429f1b0bab-AMS
A+
DNS Records
3 A records, 15 ms lookup
PASS
3 A records, 15 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 172.67.68.126, 104.26.12.111, 104.26.13.111
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:c6f, 2606:4700:20::ac43:447e, 2606:4700:20::681a:d6f
Info::
2 nameserver(s) configured
Got: dawn.ns.cloudflare.com, george.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 15 ms
Got: 15 ms
A172.67.68.126, 104.26.12.111, 104.26.13.111
AAAA2606:4700:20::681a:c6f, 2606:4700:20::ac43:447e, 2606:4700:20::681a:d6f
CNAME
NSdawn.ns.cloudflare.com, george.ns.cloudflare.com
MX
TXT
CAALookup not available with standard resolver
Resolved in 15 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

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)

A
Redirect Chain
1 redirect(s), 75 ms total
PASS
1 redirect(s), 75 ms total
Info::
Single redirect
Got: https://link.space → https://streamlabs.com/ (301)
Info::
Cross-domain redirect detected

https://link.space

35 ms · HTTP/1.1

301

https://streamlabs.com/

40 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://link.space30135 msHTTP/1.1cloudflare
2https://streamlabs.com/20040 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::681a:c6f, 2606:4700:20::ac43:447e, 2606:4700:20::681a:d6f
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::681a:c6f, 2606:4700:20::ac43:447e, 2606:4700:20::681a:d6f Connection Reachable (1 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

503https://www.link.space/
200https://link.space/

HTTP → HTTPS

301http://link.space/ https://link.space/

Consistent

A+
Domain Intelligence
link.space — via MarkMonitor Inc., 3 years, 6 months old
PASS
link.space — via MarkMonitor Inc., 3 years, 6 months old
Info::
Domain registered until Oct 13, 2026 (5 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
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.
Domain expiry

120 days

October 13, 2026

SSL certificate

52 days

Issued by Google Trust Services

Domain age

3 years, 6 months

Registered October 13, 2022

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:c6f

Registrar

MarkMonitor Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created October 13, 2022 (3 years, 6 months ago)
Expires October 13, 2026 (5 months)
Last Updated October 7, 2025
Name Servers dawn.ns.cloudflare.com, george.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::681a:c6f
Data source: rdap (0.5s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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 25 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
9 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
26 ms
Total Time Total request time from DNS lookup through full response.
26 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 9 ms Server Processing 12 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback