Skip to content
https://newsmax.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
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
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.

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

Certificate validity

91
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
  • 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, 24 ms lookup
PASS
1 A records, 24 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 64.135.21.3
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: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
Info::
2 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: 24 ms
Got: 24 ms
A64.135.21.3
AAAA
CNAME
NSdns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
MX
10 us-smtp-inbound-1.mimecast.com
10 us-smtp-inbound-2.mimecast.com
TXT
EuImLneVbV014xmQ4KZKqvrZ0D6/onP1H6hLhFxxgmJTmWD3Xfw6BT9SrvUEL9rWpDTMI/Cw5Af8ypzO...
atlassian-domain-verification=g6jjri5DHmIUPqLXWklDBInoSvHJQPsnr9AqTWTDFkKAnq621t...
spf2.0/pra mx ptr:dm-4.com ptr:newsmax.com ip4:64.135.21.10 ip4:64.135.21.11 ip4...
n5gb9ova2b2vpv6k5tgqkb2jcl
MS=6BD265554002800D41C808668AF6AAF1D5A3CAF4
SPF v=spf1 a ip4:64.135.21.10 ip4:64.135.21.11 ip4:64.135.21.15 ip4:64.135.21.20 ip4...
pinterest-site-verification=ad15f7d5e3335b981114ef7740044846
google-site-verification=ACxgDJVn0xaH-8FrtWOl93_mn4G1oF9mF3zD2lTZE6M
google-gws-recovery-domain-verification=58709473
dropbox-domain-verification=o4r61wo1xec3
openai-domain-verification=dv-nNQcyI0AHUCb7vFdrM61FCGy
anthropic-domain-verification-z1hneb=nkNipYyfjJN4u9KANrM5I6Fk0
ifjnsqc2lpc55cg9pebj4jk50k
CAALookup not available with standard resolver
Resolved in 24 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.

A+
Redirect Chain
0 redirect(s), 988 ms total
PASS
0 redirect(s), 988 ms total
Info::
Redirect overhead: 988 ms total
Got: 988 ms

https://newsmax.com

988 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://newsmax.com301988 msHTTP/1.1Microsoft-IIS/10.0
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.newsmax.com/
200https://newsmax.com/

HTTP → HTTPS

301http://newsmax.com/ https://newsmax.com/

Consistent

A
Domain Intelligence
newsmax.com — via SafeNames Ltd., 28 years, 1 months old, hosted on BROADBANDONE - BroadbandONE, LLC, US
PASS
newsmax.com — via SafeNames Ltd., 28 years, 1 months old, hosted on BROADBANDONE - BroadbandONE, LLC, US
Warning::
Domain expires in 86 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 17, 2026
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: SafeNames Ltd.
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: BROADBANDONE - BroadbandONE, LLC, US
Got: AS13645
Domain expiry

31 days

July 17, 2026

SSL certificate

91 days

Issued by GoDaddy.com, Inc.

Domain age

28 years, 1 months

Registered July 18, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

BROADBANDONE - BroadbandONE, LLC, US

ASN AS13645

64.135.21.3

Registrar

SafeNames Ltd.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar SafeNames Ltd.
Created July 18, 1998 (28 years, 1 months ago)
Expires July 17, 2026 (2 months)
Last Updated July 17, 2025
Name Servers dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
DNSSEC Not enabled
Hosting
IP Address 64.135.21.3
ASN AS13645 (BROADBANDONE - BroadbandONE, LLC, US)
Provider BROADBANDONE - BroadbandONE, LLC, US
Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 8 ms TCP Connect 96 ms TLS Handshake 290 ms Server Processing 99 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