Skip to content
https://Techex.tv

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from New York, United Stated
200 OK
Checks
17
8 PASS 9 REVIEW
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 34.111.179.208 does not match any cert SAN: 208.179.111.34.bc.googleusercontent.com
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
TLS Certificate Expiry & Recommendations
87 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: connection error, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 35 ms lookup
PASS
1 A records, 35 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.111.179.208
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: ns-1179.awsdns-19.org, ns-1929.awsdns-49.co.uk, ns-272.awsdns-34.com, ns-523.awsdns-01.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 35 ms
Got: 35 ms
A34.111.179.208
AAAA—
CNAME—
NSns-1179.awsdns-19.org, ns-1929.awsdns-49.co.uk, ns-272.awsdns-34.com, ns-523.awsdns-01.net
MX
10 techex-tv.mail.protection.outlook.com
TXT
MS=ms86054985
google-site-verification=w3OPZE_AG_VfhL63X-GS0rbNMgTYPq1I4H1yfCIv6zE
replit-verify=b4383826-b64a-4128-8255-afb91b59cb91
SPF v=spf1 a mx ip4:167.98.58.55 a:server.techex.co.uk include:amazonses.com include...
CAALookup not available with standard resolver
Resolved in 35 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 9ms across 3 resolvers (spread 17ms)
PASS
Mean 9ms across 3 resolvers (spread 17ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Quad9: 8ms
Got: 8ms via 9.9.9.9:53
Info::
Google: 19ms
Got: 19ms 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://Techex.tv

https://Techex.tv

601 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Techex.tv200601 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 24 URLs
PASS
robots.txt present, sitemap with 24 URLs
Info::
robots.txt is present
Got: 63 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 24 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 63 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /

Sitemap: https://techex.tv/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 24 entries Valid XML Yes
Sample URLs:
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.Techex.tv/
200https://Techex.tv/

Preferred variant: non-www

HTTP → HTTPS

301http://Techex.tv/ → https://techex.tv:443/

Consistent

A+
Domain Intelligence
Techex.tv — via Mesh Digital Limited, 9 years, 6 months old, hosted on Google Cloud
PASS
Techex.tv — via Mesh Digital Limited, 9 years, 6 months old, hosted on Google Cloud
Info::
Domain registered until Mar 21, 2030 (3 years, 7 months remaining)
Info::
Registrar: Mesh Digital Limited
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

1313 days

March 21, 2030

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

9 years, 6 months

Registered March 21, 2017

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.111.179.208

Registrar

Mesh Digital Limited

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar Mesh Digital Limited
Created March 21, 2017 (9 years, 6 months ago)
Expires March 21, 2030 (3 years, 7 months)
Last Updated March 20, 2025
Name Servers ns-1929.awsdns-49.co.uk, ns-272.awsdns-34.com, ns-1179.awsdns-19.org, ns-523.awsdns-01.net
Registrant Domains By Proxy, LLC
Hosting
IP Address 34.111.179.208
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: whois (1.0s)

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

Connection waterfall

DNS Lookup 11 ms TCP Connect 8 ms TLS Handshake 17 ms Server Processing 430 ms Content Transfer 119 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback