Skip to content
https://military.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
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
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.military.com/
200https://military.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
TLS Certificate Expiry & Recommendations
91 days until leaf cert expires — 5 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
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
3 A records, 206 ms lookup
PASS
3 A records, 206 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 184.34.79.220, 100.21.115.236, 52.26.30.31
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1091.awsdns-08.org, ns-170.awsdns-21.com, ns-1909.awsdns-46.co.uk, ns-919.awsdns-50.net
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
Warning::
DNS resolution is slow (206 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 206 ms
A184.34.79.220, 100.21.115.236, 52.26.30.31
AAAA
CNAME
NSns-1091.awsdns-08.org, ns-170.awsdns-21.com, ns-1909.awsdns-46.co.uk, ns-919.awsdns-50.net
MX
1 smtp.google.com
TXT
MS=ms46003472
activeprospect-domain-verification=U/gWvKrn1z4RDxgTYfT+5A==
activeprospect-domain-verification=XEz5FqPdM7Cj7I2a7mMHQA==
activeprospect-domain-verification=nfaegua1lgYwxETcazMO9w==
activeprospect-domain-verification=xffZDt2IBK0xuIBx3krBvg==
fjOeK8zyQ1DTp/Ve+2jOOhMT5lN028h4mo9GyeY/B+TVk3CaXqB4hCMRKbTUrpHE8qXEwS1AmgQJOai/...
google-gws-recovery-domain-verification=63176483
google-site-verification=F3xmTnk09wm24_bTjcgAhO5kvP0XOAKlcPf9-aR2KdQ
google-site-verification=neRmx5ZhcU2QvSrZlWPsEpQ5FP-SXuRwm9H22ZJ0xiY
ms=ms39201961
slack-domain-verification=uVmoJc9ZQNWc98KRbxTlPhMrMUzN8GA86iG64SDR
spf2.0/pra ip4:173.239.76.192/26 ip4:64.127.121.0/27 mx:intake1.miltnews.com mx...
SPF v=spf1 include:partner_c_spf.monster.com ip4:173.239.76.192/26 ip4:64.127.121.0/...
CAALookup not available with standard resolver
Resolved in 206 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.

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
Redirect Chain
1 redirect(s), 259 ms total
PASS
1 redirect(s), 259 ms total
Info::
Single redirect
Got: https://military.com → https://www.military.com/ (301)
Info::
WWW normalization redirect

https://military.com

111 ms · HTTP/1.1

301

https://www.military.com/

148 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://military.com301111 msHTTP/1.1Apache
2https://www.military.com/200148 msHTTP/1.1military.com

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 21 URLs
PASS
robots.txt present, sitemap with 21 URLs
Info::
robots.txt is present
Got: 1733 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21 entries
Info::
Sitemap index with 21 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1733 B Sitemaps referenced 1 User-agents MJ12Bot, Megaindex, AmazonAdBot, * Blocking No — crawling allowed
User-agent: *


Allow: /core/*.css$

Allow: /core/*.css?

Allow: /core/*.js$

Allow: /core/*.js?

Allow: /core/*.gif

Allow: /core/*.jpg

Allow: /core/*.jpeg

Allow: /core/*.png

Allow: /core/*.svg

Allow: /profiles/*.css$

Allow: /profiles/*.css?

Allow: /profiles/*.js$

Allow: /profiles/*.js?

Allow: /profiles/*.gif

Allow: /profiles/*.jpg

Allow: /profiles/*.jpeg

Allow: /profiles/*.png

Allow: /profiles/*.svg


Disallow: /core/

Disallow: /profiles/


Disallow: /README.txt

Disallow: /web.config


Disallow: /admin/

Disallow: /comment/reply/

Disallow: /filter/tips

Disallow: /node/add/

Disallow: /search

Disallow: /taxonomy/term/65326

Disallow: /taxonomy/term/

Disallow: /user/register/

Disallow: /user/password/

Disallow: /user/login/

Disallow: /user/logout/


Disallow: /index.php/admin/

Disallow: /index.php/comment/reply/

Disallow: /index.php/filter/tips

Disallow: /index.php/node/add/

Disallow: /index.php/search/

Disallow: /index.php/user/password/

Disallow: /index.php/user/register/

Disallow: /index.php/user/login/

Disallow: /index.php/user/logout/


Disallow: /wh=

Disallow: /?col=

Disallow: /esrc=

Disallow: /ContentFiles/NEW%20_Retirement_HR_1588.htm

Disallow: /Education/SchoolHelp.htm

Disallow: /Resources/ResourceFileView/

Disallow: /Resources/tools/

Disallow: /cs/

Disallow: /javascripts/

Disallow: /nav/

Disallow: /ppt/

Disallow: /thymeleaf/

Disallow: /member-reg/

Disallow: /newmember/

Disallow: /video/related-videos/

Disallow: /newmembers/

Disallow: /profile/

Disallow: /video/search?

Disallow: /jobsearch*


User-agent: MJ12Bot

Disallow: /

User-agent: Megaindex

Disallow: /

User-agent: AmazonAdBot

Allow: /


Sitemap: https://www.military.com/sitemap.xml
A+
Domain Intelligence
military.com — via GoDaddy.com, LLC, 29 years, 4 months old, hosted on AWS
PASS
military.com — via GoDaddy.com, LLC, 29 years, 4 months old, hosted on AWS
Info::
Domain registered until Dec 23, 2026 (8 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

191 days

December 23, 2026

SSL certificate

91 days

Issued by DigiCert Inc

Domain age

29 years, 4 months

Registered May 20, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

184.34.79.220

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 May 20, 1997 (29 years, 4 months ago)
Expires December 23, 2026 (8 months)
Last Updated November 17, 2025
Name Servers ns-1091.awsdns-08.org, ns-170.awsdns-21.com, ns-1909.awsdns-46.co.uk, ns-919.awsdns-50.net
DNSSEC Not enabled
Hosting
IP Address 184.34.79.220
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 34 ms TCP Connect 22 ms TLS Handshake 46 ms Server Processing 25 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