Skip to content
https://infoplease.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
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.infoplease.com/
200https://infoplease.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://infoplease.com/ → https://infoplease.com:443/

Consistent

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

Certificate validity

49
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
3 A records, 39 ms lookup
PASS
3 A records, 39 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.11.73, 104.26.10.73, 172.67.74.230
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::ac43:4ae6, 2606:4700:20::681a:b49, 2606:4700:20::681a:a49
Info::
2 nameserver(s) configured
Got: zahir.ns.cloudflare.com, lola.ns.cloudflare.com
Info::
5 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: 39 ms
Got: 39 ms
A104.26.11.73, 104.26.10.73, 172.67.74.230
AAAA2606:4700:20::ac43:4ae6, 2606:4700:20::681a:b49, 2606:4700:20::681a:a49
CNAME—
NSzahir.ns.cloudflare.com, lola.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=bFJDKxU5sIoJ18Q_3r_rtBU4jrITvxWHQDjPepHLIrE
google-site-verification=WI8UstmLZpR79xauvv8358gVZxYHkka7Y4-hvCB8Dpc
google-site-verification=0ceTf9WlONPiCRY6Kd8oGzOv0LNhHnlJKHMv9mjPZDE
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 39 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), 169 ms total
PASS
1 redirect(s), 169 ms total
Info::
Single redirect
Got: https://infoplease.com → https://www.infoplease.com/ (301)
Info::
WWW normalization redirect

https://infoplease.com

64 ms · HTTP/1.1

301

https://www.infoplease.com/

105 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://infoplease.com30164 msHTTP/1.1cloudflare
2https://www.infoplease.com/200105 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::ac43:4ae6, 2606:4700:20::681a:b49, 2606:4700:20::681a:a49
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::ac43:4ae6, 2606:4700:20::681a:b49, 2606:4700:20::681a:a49 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 18 URLs
PASS
robots.txt present, sitemap with 18 URLs
Info::
robots.txt is present
Got: 1813 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 18 entries
Info::
Sitemap index with 18 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1813 B Sitemaps referenced 1 User-agents rogerbot, mj12bot, dotbot, Domain Re-Animator Bot, MauiBot (crawler.feedback+wc@gmail.com), Googlebot, *, Mediapartners-Google*, Linguee Bot Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html


User-agent: Mediapartners-Google*
Disallow:

# blocking bad bots
User-agent: rogerbot
Disallow: /

User-agent: mj12bot
Disallow: /

User-agent: dotbot
Disallow: /

User-agent: Linguee Bot
Disallow: /

User-agent: Domain Re-Animator Bot
Disallow: /

User-agent: MauiBot (crawler.feedback+wc@gmail.com)
Disallow: /

User-agent: Googlebot
Disallow: /search/*

User-agent: *
Crawl-delay: 2
# CSS, JS, Images
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
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips/
Disallow: /biography/search/
Disallow: /almanac/search/
Disallow: /user/
Disallow: /topic/
Disallow: /discuss/
Disallow: /spellcheck/

# Paths (no clean URLs)
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/

#Sitemap
Sitemap: https://www.infoplease.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 18 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
infoplease.com — via CSC Corporate Domains, Inc., 29 years old
PASS
infoplease.com — via CSC Corporate Domains, Inc., 29 years old
Info::
Domain registered until Nov 19, 2026 (7 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: CSC Corporate Domains, Inc.
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.
Domain expiry

125 days

November 19, 2026

SSL certificate

49 days

Issued by Google Trust Services

Domain age

29 years

Registered September 15, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:b49

Registrar

CSC Corporate Domains, Inc.

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 CSC Corporate Domains, Inc.
Created September 15, 1997 (29 years ago)
Expires November 19, 2026 (7 months)
Last Updated November 16, 2025
Name Servers lola.ns.cloudflare.com, zahir.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::681a:b49
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 108 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
39 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
108 ms
Total Time Total request time from DNS lookup through full response.
108 ms

Connection waterfall

DNS Lookup 39 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 30 ms Content Transfer 0 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f074a2f9f07d6d2-CDG
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9f074a2f9f07d6d2-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback