Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations42 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryGoogle Cloud CDNREVIEW
A+DNS Records1 A records, 36 ms lookupPASS
| A | 34.160.33.66 |
| AAAA | — |
| CNAME | — |
| NS | ns-975.awsdns-57.net, ns-1650.awsdns-14.co.uk, ns-12.awsdns-01.com, ns-1218.awsdns-24.org |
| MX | 10 mx.zoho.com 20 mx2.zoho.com 50 mx3.zoho.com |
| TXT | tollbit-domain-verification=eae713c1bcca06f31dc53f9f86f537515315e2af2bf8fcf84dbb... SPF v=spf1 include:zohomail.com ~all google-site-verification=2sP5M5dA0InJ7mrqiweVgDwomTAxM9qMNLDue78G1aQ |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 363 ms totalPASS
https://techtimes.com
163 ms · HTTP/1.1
https://www.techtimes.com/
200 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://techtimes.com | 301 | 163 ms | HTTP/1.1 | nginx/1.27.0 |
| 2 | https://www.techtimes.com/ | 200 | 200 ms | HTTP/1.1 | nginx/1.27.0 |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 3 URLsPASS
User-agent: *
Disallow: /feeds/*
Disallow: /system/
Disallow: /rss/articles/specialcat/
Disallow: /addineyeV2l
Disallow: /eyeblaster
Disallow: /doubleclick
Disallow: /ads/sponsored
Disallow: /comment/*
Disallow: /search?q=*
Disallow: /search/site*
Disallow: /tool/logout*
Disallow: /corporate/newsletter/signup?*
User-agent: Applebot-Extended
User-agent: AliyunSecBot
User-agent: Amazonbot
User-agent: Arquivo-web-crawler
User-agent: AwarioRssBot
User-agent: AwarioSmartBot
User-agent: anthropic-ai
User-agent: AudigentAdBot
User-agent: BLEXBot
User-agent: Bytespider
User-agent: Buck
User-agent: CCBot
User-agent: coccocbot-web
User-agent: cohere-ai
User-agent: ClaudeBot
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: Claude-Web
User-agent: DataForSeoBot
User-agent: DuckAssistBot
User-agent: FacebookBot
User-agent: ImageSift
User-agent: JenkersBot
User-agent: Jetslide
User-agent: MoodleBot
User-agent: meta-externalagent
User-agent: Meta-ExternalAgent
User-agent: Meta-ExternalFetcher
User-agent: meta-externalfetcher
User-agent: MyCentralAIScraperBot
User-agent: Mojeek
User-agent: news-please
User-agent: OAI-SearchBot
User-agent: omgili
User-agent: omgilibot
User-agent: peer39_crawler
User-agent: peer39_crawler/1.0
User-agent: PetalBot
User-Agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Poseidon Research Crawler
User-agent: quillbot.com
User-agent: Quora-Bot
User-agent: Scrapy
User-agent: Seekr
User-agent: SeekrBot
User-agent: SeznamBot
User-agent: SeznamHomepageCrawler
User-agent: scalepostAI
User-agent: SentiOne
User-agent: TaraGroup Intelligent Bot
User-agent: Timpibot
User-agent: TurnitinBot
User-agent: ViennaTinyBot
User-Agent: yacy
User-agent: YandexAdditional
User-agent: YandexAdditionalBot
User-agent: YouBot
Sitemap: https://www.techtimes.com/sitemap.xml
Sitemap: https://www.techtimes.com/googlenews.xml
A+Domain Intelligencetechtimes.com — via TLDS L.L.C. d/b/a SRSPlus, 26 years, 8 months old, hosted on Google CloudPASS
179 days
December 12, 2026
42 days
Issued by Google Trust Services
26 years, 8 months
Registered December 12, 1999
Not enabled
Protects against DNS spoofing
Google Cloud
ASN AS396982
34.160.33.66
TLDS L.L.C. d/b/a SRSPlus
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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