Skip to content
https://t.ly

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
97
GRADE
A+
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
55 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

55
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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: CDG)
Got: cf-ray: 9eff214a5c6bf6dd-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9eff214a5c6bf6dd-CDG
A+
DNS Records
2 A records, 37 ms lookup
PASS
2 A records, 37 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.20.7.133, 104.20.6.133
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:685, 2606:4700:10::6814:785
Info::
2 nameserver(s) configured
Got: vida.ns.cloudflare.com, ivan.ns.cloudflare.com
Info::
6 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 37 ms
Got: 37 ms
A104.20.7.133, 104.20.6.133
AAAA2606:4700:10::6814:685, 2606:4700:10::6814:785
CNAME
NSvida.ns.cloudflare.com, ivan.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
15 s76xmsvkv53zk4mecsx6vhsxovktess7wypymzdgrh3ajpxofa4a.mx-verification.google.com
TXT
ahrefs-site-verification_ec855967deaadda458c24ee0ae05e82d0a144e2d91f9ff840ccb2e1...
google-site-verification=VWAuVVDbDERkwD7j0HffRxV_4ZYNSlmSFHZZQ6mBZLg
google-site-verification=mBi24EbWStadX31zb-0MRYyAHCvogI_TdLFHFh4ULSk
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 37 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.

A+
Redirect Chain
0 redirect(s), 61 ms total
PASS
0 redirect(s), 61 ms total

https://t.ly

61 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://t.ly40361 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::6814:685, 2606:4700:10::6814:785
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::6814:685, 2606:4700:10::6814:785 Connection Reachable (17 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 57 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 57 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
Sitemap: https://t.ly/sitemap.xml
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.t.ly/
200https://t.ly/

Preferred variant: non-www

HTTP → HTTPS

301http://t.ly/ https://t.ly/

Consistent

A+
Domain Intelligence
t.ly — via Libyan Spider Network (int), 16 years, 4 months old
PASS
t.ly — via Libyan Spider Network (int), 16 years, 4 months old
Info::
Domain registered until Mar 25, 2030 (3 years, 11 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: Libyan Spider Network (int)
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

1349 days

March 25, 2030

SSL certificate

55 days

Issued by Google Trust Services

Domain age

16 years, 4 months

Registered March 1, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::6814:685

Registrar

Libyan Spider Network (int)

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 Libyan Spider Network (int)
Created March 1, 2010 (16 years, 4 months ago)
Expires March 25, 2030 (3 years, 11 months)
Last Updated January 28, 2026
Name Servers vida.ns.cloudflare.com, ivan.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::6814:685
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 30 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 21 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