Skip to content
https://militarytimes.com

Infrastructure

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

https://militarytimes.com

2178 ms · HTTP/1.1

301

https://www.militarytimes.com:443/

174 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://militarytimes.com3012178 msHTTP/1.1awselb/2.0
2https://www.militarytimes.com:443/200174 msHTTP/1.1openresty

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://militarytimes.com/ → https://www.militarytimes.com:443/

Consistent

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

Connection waterfall

DNS Lookup 100 ms TCP Connect 235 ms TLS Handshake 473 ms Server Processing 236 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
192 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

192
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, 200 ms lookup
PASS
6 A records, 200 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 23.23.220.93, 44.206.34.136, 54.242.199.245, 52.5.205.156, 34.195.125.84, 52.54.219.196
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1358.awsdns-41.org, ns-1785.awsdns-31.co.uk, ns-438.awsdns-54.com, ns-576.awsdns-08.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: 200 ms
Got: 200 ms
A23.23.220.93, 44.206.34.136, 54.242.199.245, 52.5.205.156, 34.195.125.84, 52.54.219.196
AAAA—
CNAME—
NSns-1358.awsdns-41.org, ns-1785.awsdns-31.co.uk, ns-438.awsdns-54.com, ns-576.awsdns-08.net
MX
100 usb-smtp-inbound-2.mimecast.com
100 usb-smtp-inbound-1.mimecast.com
TXT
0ed1fe018a2ff200707720451391ad6391005b06bb
anthropic-domain-verification-e9g2v9=cg0uRdIsAtwuzGhAWkb9iRDxt
facebook-domain-verification=tpoxcu3fnnrwm8q2n3yj3fba8cyve4
google-site-verification=A1c0_zdDDzwHwXQ3Qx3LXZLJFw8IFIcaQ9ZeP669UmE
google-site-verification=C-VRM23ylQqHKzC0b6eDbMuuS_AyOYsYq21nrgyiaX4
SPF v=spf1 include:usb._netblocks.mimecast.com include:spf.protection.outlook.com in...
yahoo-verification-key=H/QFaCE9OlX9LNBXoIEs/P1wJd1NLzHlS3DHngR5esA=
CAALookup not available with standard resolver
Resolved in 200 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+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 258 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 258 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /search/
Disallow: /preview/
Disallow: /composer-preview/

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

Sitemap: https://www.militarytimes.com/arc/outboundfeeds/sitemap-news/?outputType=xml
sitemap.xml 200 OK
Type Sitemap Index URLs 8 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
militarytimes.com — via GoDaddy.com, LLC, 25 years, 2 months old, hosted on AWS
PASS
militarytimes.com — via GoDaddy.com, LLC, 25 years, 2 months old, hosted on AWS
Info::
Domain registered until Jun 25, 2029 (3 years, 2 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: AS14618
Domain expiry

1108 days

June 25, 2029

SSL certificate

192 days

Issued by Amazon

Domain age

25 years, 2 months

Registered June 25, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

34.195.125.84

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created June 25, 2001 (25 years, 2 months ago)
Expires June 25, 2029 (3 years, 2 months)
Last Updated May 27, 2025
Name Servers ns-1358.awsdns-41.org, ns-1785.awsdns-31.co.uk, ns-438.awsdns-54.com, ns-576.awsdns-08.net
DNSSEC Not enabled
Hosting
IP Address 34.195.125.84
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.6s)

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