Skip to content
https://antaranews.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
1
REVIEW
6
PASS
2
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
2 PASS 6 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.

B
Redirect Chain
1 redirect(s), 2250 ms total
REVIEW
1 redirect(s), 2250 ms total
Info::
Single redirect
Got: https://antaranews.com → https://www.antaranews.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2250 ms total
Got: 2250 ms

https://antaranews.com

1241 ms · HTTP/1.1

301

https://www.antaranews.com/

1010 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://antaranews.com3011241 msHTTP/1.1
2https://www.antaranews.com/2001010 msHTTP/1.1antara1

See the visual redirect chain in the HTTP Probe tab →

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 179 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 179 B Sitemaps referenced 0 User-agents *, BLP_bbot/0.1, BLP_bbot, ClaudeBot Blocking No — crawling allowed
User-agent: *

Allow: /

Disallow: /ajax/*

Disallow: /ucnews/*


User-agent: BLP_bbot/0.1

Disallow: /


User-agent: BLP_bbot

Disallow: /


User-agent: ClaudeBot

Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.antaranews.com/
200https://antaranews.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://antaranews.com/ https://www.antaranews.com/

Consistent

B
HTTP Probe Timing
Total 1124 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
121 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
333 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
339 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.12 s
Total Time Total request time from DNS lookup through full response.
1.12 s

Connection waterfall

DNS Lookup 121 ms TCP Connect 333 ms TLS Handshake 339 ms Server Processing 332 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
129 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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, 371 ms lookup
PASS
1 A records, 371 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 183.182.92.213
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns1.he.net, ns2.he.net, ns5.he.net, ns3.he.net, ns4.he.net
Info::
3 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
Warning::
DNS resolution is slow (371 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 371 ms
A183.182.92.213
AAAA
CNAME
NSns1.he.net, ns2.he.net, ns5.he.net, ns3.he.net, ns4.he.net
MX
10 mx.zoho.com
10 mx3.zoho.com
20 mx2.zoho.com
TXT
google-site-verification=MQDbZsgaH1cobKjZ2BVxR7Q0CBVYESntMkMlzlLWGo0
SPF v=spf1 ip4:183.182.92.130 ip4:183.182.92.213 ip4:183.182.92.150 ip4:183.182.92.2...
firebase=antaranews-1190
zoho-verification=zb52708814.zmverify.zoho.com
CAALookup not available with standard resolver
Resolved in 371 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Domain Intelligence
antaranews.com — via NameCheap, Inc., 23 years, 6 months old, hosted on ANTARA-AS-ID LKBN ANTARA, ID
PASS
antaranews.com — via NameCheap, Inc., 23 years, 6 months old, hosted on ANTARA-AS-ID LKBN ANTARA, ID
Info::
Domain registered until Feb 18, 2030 (3 years, 10 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: NameCheap, 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: ANTARA-AS-ID LKBN ANTARA, ID
Got: AS46016
Domain expiry

1343 days

February 18, 2030

SSL certificate

129 days

Issued by Sectigo Limited

Domain age

23 years, 6 months

Registered February 18, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ANTARA-AS-ID LKBN ANTARA, ID

ASN AS46016

183.182.92.213

Registrar

NameCheap, Inc.

Unlocked 5 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 NameCheap, Inc.
Created February 18, 2003 (23 years, 6 months ago)
Expires February 18, 2030 (3 years, 10 months)
Last Updated October 4, 2025
Name Servers ns1.he.net, ns2.he.net, ns3.he.net, ns4.he.net, ns5.he.net
DNSSEC Not enabled
Hosting
IP Address 183.182.92.213
ASN AS46016 (ANTARA-AS-ID LKBN ANTARA, ID)
Provider ANTARA-AS-ID LKBN ANTARA, ID
Data source: rdap (0.8s)

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

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

Send Feedback