Skip to content
https://t.me/+7CNbkKxrQEJkMmI1

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
2
REVIEW
7
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 7 REVIEW 2 FIX
D
TLS Certificate Expiry & Recommendations
Action
9 days until leaf cert expires — 5 issues to address
FIX

Certificate validity

9
days left
0d 30d 60d 90d+
Renew urgently — under 14 days remaining

Recommended actions

  • Renew certificate — 9 days remaining
  • 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
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. 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)
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.
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 149.154.167.99: lookup 149.154.167.99: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2001:67c:4e8:f004::9: lookup 2001:67c:4e8:f004::9: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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.

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Warning::
Trailing slash inconsistency — both versions serve content
Got: Both with/without trailing slash return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.t.me/+7CNbkKxrQEJkMmI1
200https://t.me/+7CNbkKxrQEJkMmI1

Inconsistent — duplicate content risk

Trailing Slash

200https://t.me/+7CNbkKxrQEJkMmI1/
200https://t.me/+7CNbkKxrQEJkMmI1

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://t.me/+7CNbkKxrQEJkMmI1 → https://t.me/+7CNbkKxrQEJkMmI1

Consistent

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, 30 ms lookup
PASS
1 A records, 30 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-b3.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com
Info::
No MX records — email not configured via DNS
Info::
SPF record present in TXT
Info::
DNS resolution time: 30 ms
Got: 30 ms
A149.154.167.99
AAAA2001:67c:4e8:f004::9
CNAME—
NSns-cloud-b1.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com
MX—
TXT
SPF v=spf1 -all
CAALookup not available with standard resolver
Resolved in 30 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 11ms across 3 resolvers (spread 16ms)
PASS
Mean 11ms across 3 resolvers (spread 16ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 16ms
Got: 16ms via 8.8.8.8:53
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://t.me/+7CNbkKxrQEJkMmI1

https://t.me/+7CNbkKxrQEJkMmI1

102 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://t.me/+7CNbkKxrQEJkMmI1200102 msHTTP/1.1nginx/1.30.1
A+
IPv6 Readiness
IPv6 reachable (30 ms)
PASS
IPv6 reachable (30 ms)
Info::
IPv6 is configured and reachable at 2001:67c:4e8:f004::9
Got: 30 ms connect
IPv6 Ready
AAAA Records 2001:67c:4e8:f004::9 Connection Reachable (30 ms)
A+
Domain Intelligence
t.me — via GoDaddy.com, LLC, 16 years, 8 months old
PASS
t.me — via GoDaddy.com, LLC, 16 years, 8 months old
Info::
Domain registered until May 20, 2035 (8 years, 7 months remaining)
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

3109 days

May 20, 2035

SSL certificate

9 days

Issued by GoDaddy.com, Inc.

Domain age

16 years, 8 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
  • Renew the TLS certificate or verify auto-renewal is working
Registrar GoDaddy.com, LLC
Created May 20, 2010 (16 years, 8 months ago)
Expires May 20, 2035 (8 years, 7 months)
Last Updated August 11, 2026
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.1s)

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

A+
HTTP Probe Timing
Total 119 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
18 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.
29 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
119 ms
Total Time Total request time from DNS lookup through full response.
119 ms

Connection waterfall

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

Send Feedback