Skip to content
https://defensenews.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.defensenews.com/
200https://defensenews.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://defensenews.com/ https://www.defensenews.com:443/

Consistent

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

Certificate validity

226
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
6 A records, 53 ms lookup
PASS
6 A records, 53 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 52.54.219.196, 44.206.34.136, 54.242.199.245, 34.195.125.84, 52.5.205.156, 23.23.220.93
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1818.awsdns-35.co.uk, ns-896.awsdns-48.net, ns-1491.awsdns-58.org, ns-16.awsdns-02.com
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: 53 ms
Got: 53 ms
A52.54.219.196, 44.206.34.136, 54.242.199.245, 34.195.125.84, 52.5.205.156, 23.23.220.93
AAAA
CNAME
NSns-1818.awsdns-35.co.uk, ns-896.awsdns-48.net, ns-1491.awsdns-58.org, ns-16.awsdns-02.com
MX
100 usb-smtp-inbound-2.mimecast.com
100 usb-smtp-inbound-1.mimecast.com
TXT
0ed1fe018ae3503ba13e154d7d8850d85d9819dbe1
google-site-verification=oZB4fh3dPrxODQfF-aS9yH_UBGlhuN8B0Zk8ztKmsV8
facebook-domain-verification=oh3bu0rylm76w0f4mhwsfiau9g8ss1
google-site-verification=QQz5PxwRvdcPJQtGeVezaFkazlvgN7s76NnNET3S34Q
yahoo-verification-key=xA8ldrWI8vepDwHclyqIN39CvrXDk65KrARbX/NC2F8=
google-site-verification=asHmDbkNbwUeKlC5UQ4X0hwtu-vqWERiMR2I9qQEjz8
SPF v=spf1 include:usb._netblocks.mimecast.com include:spf.protection.outlook.com in...
MS=ms33588418
CAALookup not available with standard resolver
Resolved in 53 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), 945 ms total
PASS
1 redirect(s), 945 ms total
Info::
Single redirect
Got: https://defensenews.com → https://www.defensenews.com:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 945 ms total
Got: 945 ms

https://defensenews.com

388 ms · HTTP/1.1

301

https://www.defensenews.com:443/

557 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://defensenews.com301388 msHTTP/1.1awselb/2.0
2https://www.defensenews.com:443/200557 msHTTP/1.1openresty

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 254 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 254 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /search/
Disallow: /preview/
Disallow: /composer-preview/

Sitemap: https://www.defensenews.com/arc/outboundfeeds/sitemap-index/?outputType=xml

Sitemap: https://www.defensenews.com/arc/outboundfeeds/sitemap-news/?outputType=xml


A+
Domain Intelligence
defensenews.com — via GoDaddy.com, LLC, 31 years old, hosted on AWS
PASS
defensenews.com — via GoDaddy.com, LLC, 31 years old, hosted on AWS
Info::
Domain registered until Sep 9, 2026 (4 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: GoDaddy.com, 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: AWS
Got: AS16509
Domain expiry

87 days

September 9, 2026

SSL certificate

226 days

Issued by Amazon

Domain age

31 years

Registered September 10, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

44.206.34.136

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created September 10, 1995 (31 years ago)
Expires September 9, 2026 (4 months)
Last Updated September 9, 2025
Name Servers ns-1491.awsdns-58.org, ns-16.awsdns-02.com, ns-1818.awsdns-35.co.uk, ns-896.awsdns-48.net
DNSSEC Not enabled
Hosting
IP Address 44.206.34.136
ASN AS16509 (AMAZON-02 - 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 447 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
54 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.
447 ms
Total Time Total request time from DNS lookup through full response.
447 ms

Connection waterfall

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