Skip to content
https://t.me

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Singapore, Singapore
302 Found
Checks
9
5 PASS 2 REVIEW 2 FIX
D
HTTP Probe Timing
Action
Total 2451 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
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.
159 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
160 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.45 s
Total Time Total request time from DNS lookup through full response.
2.45 s

Connection waterfall

DNS Lookup 3 ms TCP Connect 159 ms TLS Handshake 160 ms Server Processing 2.13 s Content Transfer 0 ms
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
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
220 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
A+
DNS Records
1 A records, 11 ms lookup
PASS
1 A records, 11 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 149.154.167.99
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2001:67c:4e8:f004::9
Info::
4 nameserver(s) configured
Got: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b3.googledomains.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::
SPF record present in TXT
Info::
DNS resolution time: 11 ms
Got: 11 ms
A149.154.167.99
AAAA2001:67c:4e8:f004::9
CNAME—
NSns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b3.googledomains.com
MX—
TXT
SPF v=spf1 -all
CAALookup not available with standard resolver
Resolved in 11 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

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
No redirect data available
PASS
No redirect data available
Info::
No redirect data captured
A+
IPv6 Readiness
IPv6 reachable (156 ms)
PASS
IPv6 reachable (156 ms)
Info::
IPv6 is configured and reachable at 2001:67c:4e8:f004::9
Got: 156 ms connect
IPv6 Ready
AAAA Records 2001:67c:4e8:f004::9 Connection Reachable (156 ms)
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

302https://www.t.me/
200https://t.me/

Preferred variant: non-www

HTTP → HTTPS

301http://t.me/ → https://t.me/

Consistent

A
Domain Intelligence
t.me — via GoDaddy.com, LLC, 16 years, 1 months old
PASS
t.me — via GoDaddy.com, LLC, 16 years, 1 months old
Warning::
Domain expires in 34 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 20, 2026
Info::
Registrar: GoDaddy.com, LLC
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Domain expiry

EXPIRED

May 20, 2026

SSL certificate

220 days

Issued by GoDaddy.com, Inc.

Domain age

16 years, 1 months

Registered May 20, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2001:67c:4e8:f004::9

Registrar

GoDaddy.com, LLC

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
Registrar GoDaddy.com, LLC
Created May 20, 2010 (16 years, 1 months ago)
Expires May 20, 2026 (1 months)
Last Updated July 4, 2025
Name Servers ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
Registrant Domains By Proxy, LLC
Hosting
IP Address 2001:67c:4e8:f004::9
Data source: whois (1.9s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

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

Source: ICANN renewal policy

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Send Feedback