Skip to content
https://ibtimes.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
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.

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
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ibtimes.com/
200https://ibtimes.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ibtimes.com/ → https://www.ibtimes.com/

Consistent

B
TLS Certificate Expiry & Recommendations
170 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
2 A records, 44 ms lookup
PASS
2 A records, 44 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 54.234.68.27, 174.129.224.216
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-770.awsdns-32.net, ns-1444.awsdns-52.org, ns-1620.awsdns-10.co.uk, ns-214.awsdns-26.com
Info::
5 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: 44 ms
Got: 44 ms
A54.234.68.27, 174.129.224.216
AAAA—
CNAME—
NSns-770.awsdns-32.net, ns-1444.awsdns-52.org, ns-1620.awsdns-10.co.uk, ns-214.awsdns-26.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
tollbit-domain-verification=a0dcb1a595eac375c4e76525609ac33b4b7bb056db4c973eac6f...
google-site-verification=naT11XtdbY0jkYnEmosMoXjM1LMaKIVJECqE7-U42Bc
facebook-domain-verification=lqihwhw827n6skd88ntbdy2r5z3e1i
ahrefs-site-verification_e79c43e8b729d28aac502a5647137b517464e5dd71fed60c0d52c98...
google-site-verification=tdo2VCPIsJCRlFscYNbsfjAOy8wt2MRc_0qo5Qy4PLw
globalsign-domain-verification=KaParXxs1OHDy7o8CMbPpHBN-2m_mzwdPqKMMQ66a6
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 44 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
1 redirect(s), 909 ms total
PASS
1 redirect(s), 909 ms total
Info::
Single redirect
Got: https://ibtimes.com → https://www.ibtimes.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 909 ms total
Got: 909 ms

https://ibtimes.com

388 ms · HTTP/1.1

301

https://www.ibtimes.com/

522 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ibtimes.com301388 msHTTP/1.1Varnish
2https://www.ibtimes.com/200522 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 34 URLs
PASS
robots.txt present, sitemap with 34 URLs
Info::
robots.txt is present
Got: 2453 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 34 entries
Info::
Sitemap index with 34 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2453 B Sitemaps referenced 2 User-agents SeznamHomepageCrawler, YandexAdditionalBot, AwarioSmartBot, ImageSift, Seekr, Jetslide, Timpibot, yacy, cohere-ai, FacebookBot, MoodleBot, MyCentralAIScraperBot, PerplexityBot, YandexAdditional, AliyunSecBot, AwarioRssBot, meta-externalfetcher, SeznamBot, TurnitinBot, *, DuckAssistBot, omgilibot, peer39_crawler/1.0, Quora-Bot, SeekrBot, SentiOne, Mojeek, OAI-SearchBot, quillbot.com, YouBot, anthropic-ai, TaraGroup Intelligent Bot, peer39_crawler, PetalBot, scalepostAI, CCBot, coccocbot-web, Meta-ExternalAgent, Perplexity-User, Arquivo-web-crawler, BLEXBot, DataForSeoBot, meta-externalagent, Scrapy, ViennaTinyBot, AudigentAdBot, ClaudeBot, Claude-Web, omgili, Applebot-Extended, Buck, JenkersBot, Meta-ExternalFetcher, Poseidon Research Crawler, Amazonbot, Bytespider, Claude-SearchBot, Claude-User, news-please Blocking No — crawling allowed
# This is the robots.txt file for ibtimes.com


# The content on IBTimes is protected by our terms of service and copyright policies.  

# Unauthorized use of our content is prohibited. This includes, but is not limited to:  

# use by large language models (LLMs), machine learning systems, artificial intelligence  

# technologies, automated scraping, or any commercial exploitation without prior written consent.  

# For licensing or permission requests, please contact: licensing@ibt.com


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

Disallow: /


Sitemap: https://www.ibtimes.com/sitemap.xml

Sitemap: https://www.ibtimes.com/googlenews.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 34 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
ibtimes.com — via MarkMonitor Inc., 20 years, 7 months old, hosted on AWS
PASS
ibtimes.com — via MarkMonitor Inc., 20 years, 7 months old, hosted on AWS
Info::
Domain registered until Dec 12, 2026 (7 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: MarkMonitor Inc.
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.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

148 days

December 12, 2026

SSL certificate

170 days

Issued by Amazon

Domain age

20 years, 7 months

Registered December 12, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

54.234.68.27

Registrar

MarkMonitor Inc.

Unlocked 4 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 MarkMonitor Inc.
Created December 12, 2005 (20 years, 7 months ago)
Expires December 12, 2026 (7 months)
Last Updated November 10, 2025
Name Servers ns-1444.awsdns-52.org, ns-1620.awsdns-10.co.uk, ns-214.awsdns-26.com, ns-770.awsdns-32.net
DNSSEC Not enabled
Hosting
IP Address 54.234.68.27
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 37 ms TCP Connect 98 ms TLS Handshake 197 ms Server Processing 100 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