Skip to content
https://ipsnews.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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), 1349 ms total
REVIEW
1 redirect(s), 1349 ms total
Info::
Single redirect
Got: https://ipsnews.net → https://www.ipsnews.net/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1349 ms total
Got: 1349 ms

https://ipsnews.net

669 ms · HTTP/1.1

301

https://www.ipsnews.net/

680 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ipsnews.net301669 msHTTP/1.1Apache
2https://www.ipsnews.net/200680 msHTTP/1.1Apache

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
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.ipsnews.net/
200https://ipsnews.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ipsnews.net/ https://ipsnews.net/

Consistent

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

Certificate validity

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

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
A+
DNS Records
1 A records, 54 ms lookup
PASS
1 A records, 54 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 72.52.191.145
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns.liquidweb.com, ns1.liquidweb.com
Info::
1 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: 54 ms
Got: 54 ms
A72.52.191.145
AAAA
CNAME
NSns.liquidweb.com, ns1.liquidweb.com
MX
10 ipsnews.net
TXT
kaboozt-publisher-token=721fc2d831228cf556c90117cacb9192
globalsign-domain-verification=SOy6OJyOOncyx-ptvPSPUPs0k-MVR5S_Tu_ZYGBdOZ
SPF v=spf1 +a +mx +ip4:67.43.4.144 ~all
google-site-verification=-7EoiPalh2o3k0NOrDYvbLcW44fGNGxfJHI_zFosbtg
CAALookup not available with standard resolver
Resolved in 54 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+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 1415 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1415 B Sitemaps referenced 2 User-agents Googlebot-Video, Bingbot, LinkedInBot, WhatsApp, ClaudeBot, anthropic-ai, cohere-ai, *, Googlebot-Image, DuckDuckBot, Twitterbot, PerplexityBot, Googlebot-News, Yandex, facebookexternalhit, Googlebot, Google-Extended, msnbot, Applebot-Extended, GPTBot, CCBot Blocking No — crawling allowed
# == GOOGLE ==

User-agent: Googlebot

Disallow:


User-agent: Googlebot-Image

Disallow:


User-agent: Googlebot-Video

Disallow:


User-agent: Googlebot-News

Disallow:


# Google-Extended: AI overview training (allow for visibility in AI search)

User-agent: Google-Extended

Disallow:


# == BING / MICROSOFT ==

User-agent: Bingbot

Disallow:

Crawl-delay: 5

User-agent: msnbot

Disallow:

Crawl-delay: 5

# == OTHER SEARCH ENGINES ==

User-agent: DuckDuckBot

Disallow:


User-agent: Yandex

Disallow:

Crawl-delay: 10

# == SOCIAL MEDIA (critical for article sharing) ==

User-agent: Twitterbot

Disallow:


User-agent: facebookexternalhit

Disallow:


User-agent: LinkedInBot

Disallow:


User-agent: WhatsApp

Disallow:


# == AI RETRIEVAL BOTS (allows IPS content in AI answers) ==

User-agent: PerplexityBot

Disallow:


User-agent: ClaudeBot

Disallow:


User-agent: Applebot-Extended

Disallow:


# == AI TRAINING BOTS (blocked - no value exchange) ==

User-agent: GPTBot

Disallow: /


User-agent: CCBot

Disallow: /


User-agent: anthropic-ai

Disallow: /


User-agent: cohere-ai

Disallow: /


# == ALL OTHER BOTS: block sensitive areas only ==

User-agent: *

Disallow: /wp-admin/

Disallow: /wp-login.php

Disallow: /wp-json/

Allow: /wp-admin/admin-ajax.php


# == SITEMAPS ==

Sitemap: https://ipsnews.net/sitemap_index.xml

Sitemap: https://ipsnews.net/news-sitemap.xml
A+
Domain Intelligence
ipsnews.net — via Network Solutions, LLC, 26 years, 3 months old, hosted on LIQUIDWEB - Liquid Web, L.L.C, US
PASS
ipsnews.net — via Network Solutions, LLC, 26 years, 3 months old, hosted on LIQUIDWEB - Liquid Web, L.L.C, US
Info::
Domain registered until May 31, 2029 (3 years, 1 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: Network Solutions, LLC
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: LIQUIDWEB - Liquid Web, L.L.C, US
Got: AS32244
Domain expiry

1080 days

May 31, 2029

SSL certificate

33 days

Issued by Let's Encrypt

Domain age

26 years, 3 months

Registered May 31, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

LIQUIDWEB - Liquid Web, L.L.C, US

ASN AS32244

72.52.191.145

Registrar

Network Solutions, LLC

Unlocked 2 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 Network Solutions, LLC
Created May 31, 2000 (26 years, 3 months ago)
Expires May 31, 2029 (3 years, 1 months)
Last Updated April 1, 2026
Name Servers ns.liquidweb.com, ns1.liquidweb.com
DNSSEC Not enabled
Hosting
IP Address 72.52.191.145
ASN AS32244 (LIQUIDWEB - Liquid Web, L.L.C, US)
Provider LIQUIDWEB - Liquid Web, L.L.C, US
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 795 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
115 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
123 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
796 ms
Total Time Total request time from DNS lookup through full response.
796 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 115 ms TLS Handshake 123 ms Server Processing 512 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