Skip to content
https://globalsecurity.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from New York, United Stated
302 Found
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.

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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1344 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1344 B Sitemaps referenced 0 User-agents ClaudeBot, anthropic-ai, FacebookBot, Mediapartners-Google, GPTBot, Google-Extended, Googlebot, *, cohere-ai, Diffbot, ImagesiftBot, ChatGLM-Spider, CCBot, Bytespider, PerplexityBot, Omgilibot, Applebot-Extended Blocking No — crawling allowed
User-agent: Mediapartners-Google

Disallow:


User-agent: *

Disallow: /phpadsnew/

Disallow: /cgi-bin/texis.cgi/webinator/search/

Allow: /


# Block OpenAI GPTBot

User-agent: GPTBot

Disallow: /


# Block Anthropic ClaudeBot

User-agent: ClaudeBot

Disallow: /


# Block Google Bard/Gemini training

User-agent: Google-Extended

Disallow: /


# Block Common Crawl

User-agent: CCBot

Disallow: /


# Block Bytespider (TikTok/ByteDance)

User-agent: Bytespider

Disallow: /


# Block Perplexity AI

User-agent: PerplexityBot

Disallow: /


# Block other major AI bots

User-agent: anthropic-ai

Disallow: /


User-agent: cohere-ai

Disallow: /


User-agent: Omgilibot

Disallow: /


User-agent: FacebookBot

Disallow: /


User-agent: Applebot-Extended

Disallow: /


User-agent: ChatGLM-Spider

Disallow: /


User-agent: Diffbot

Disallow: /


User-agent: ImagesiftBot

Disallow: /


User-agent: Googlebot

Disallow:/intell/library/news/

Disallow:/military/library/news/

Disallow:/security/library/news/

Disallow:/space/library/news/

Disallow:/wmd/library/news/

Disallow:/auto/

Disallow:/books/

Disallow:/conferences/

Disallow:/flvplayer/

Disallow:/education/

Disallow:/gifts/

Disallow:/Library/

Disallow:/loans/

Disallow:/search/

Disallow:/sponsor/

Disallow:/stitial/

Disallow:/travel/

Disallow:/_inc/frames/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.globalsecurity.org/
200https://globalsecurity.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://globalsecurity.org/ https://www.globalsecurity.org/

Use 301 (permanent) instead of 302 (temporary)

C
TLS Certificate Expiry & Recommendations
Action
17 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

17
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 17 days remaining
  • 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
1 A records, 56 ms lookup
PASS
1 A records, 56 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 13.68.95.120
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: ns18.worldnic.com, ns17.worldnic.com
Info::
3 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: 56 ms
Got: 56 ms
A13.68.95.120
AAAA
CNAME
NSns18.worldnic.com, ns17.worldnic.com
MX
10 globalsecurity-org.relay1a.spamh.com
20 globalsecurity-org.relay1b.spamh.com
30 globalsecurity-org.relay1c.spamh.com
TXT
SPF v=spf1 a:webmail.globalsecurity.org a:globalsecurity.org ip4:104.46.194.29/32 ip...
CAALookup not available with standard resolver
Resolved in 56 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
1 redirect(s), 187 ms total
PASS
1 redirect(s), 187 ms total
Info::
Single redirect
Got: https://globalsecurity.org → https://www.globalsecurity.org:443/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://globalsecurity.org

https://globalsecurity.org

75 ms · HTTP/1.1

302

https://www.globalsecurity.org:443/

112 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://globalsecurity.org30275 msHTTP/1.1Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16
2https://www.globalsecurity.org:443/200112 msHTTP/1.1Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips PHP/5.4.16

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Domain Intelligence
globalsecurity.org — via Network Solutions, LLC, 27 years, 4 months old, hosted on Microsoft Azure
PASS
globalsecurity.org — via Network Solutions, LLC, 27 years, 4 months old, hosted on Microsoft Azure
Info::
Domain registered until Apr 30, 2032 (6 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: Microsoft Azure
Got: AS8075
Domain expiry

2148 days

April 30, 2032

SSL certificate

17 days

Issued by Let's Encrypt

Domain age

27 years, 4 months

Registered April 30, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

13.68.95.120

Registrar

Network Solutions, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Network Solutions, LLC
Created April 30, 1999 (27 years, 4 months ago)
Expires April 30, 2032 (6 years, 1 months)
Last Updated November 3, 2024
Name Servers ns17.worldnic.com, ns18.worldnic.com
DNSSEC Not enabled
Hosting
IP Address 13.68.95.120
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
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 73 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
24 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
12 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
26 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
74 ms
Total Time Total request time from DNS lookup through full response.
74 ms

Connection waterfall

DNS Lookup 24 ms TCP Connect 12 ms TLS Handshake 26 ms Server Processing 12 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