Skip to content
https://nea.org

Infrastructure

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nea.org/ https://nea.org/

Consistent

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

Certificate validity

70
days left
0d 30d 60d 90d+

Recommended actions

  • 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
2 A records, 197 ms lookup
PASS
2 A records, 197 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.19.252.49, 104.19.251.49
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns11.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns10.dnsmadeeasy.com, ns15.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns12.dnsmadeeasy.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: 197 ms
Got: 197 ms
A104.19.252.49, 104.19.251.49
AAAA
CNAME
NSns11.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns10.dnsmadeeasy.com, ns15.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns12.dnsmadeeasy.com
MX
0 nea-org.mail.protection.outlook.com
5 vanguardmx.nea.org
TXT
google-site-verification=l1-hxV01rP_nDtj-u4dHvnq94UgFo1iDK4kFXJOpXPE
facebook-domain-verification=reynsnajceh78j76iusrgi6z8a88uj
_t22jxqd0ciu1u2csmit1wy3iuyeavc5
WLoa5H6KnLTyrJqpljVLxQK6w2eZPpdEpmacEs/5tPxJCfkbBhzsWMxhfHxnyNtxD63bjw6Np80TGymS...
MS=ms13966354
7b8v8c021k4bqly6xv086tjd6q69zbfq
_tlsw6qtzf1a0pr9ofaekuv60x2ebsyb
SPF v=spf1 mx ip4:199.223.129.0/24 ip4:65.118.130.12/32 ip4:198.2.180.200/32 ip4:198...
ca3-ffe8238d8ae24bc1bab0fefdc65d5049
fastly-domain-delegation-w87CMtb2oI8fSWwLpiNS-288608-2020-09-22
BC0bbBq15WSNpkX80pYqv1fjvFcfHqAvDdN+OwDOXNvTPHfkdgRkxZOoQth+gGHsUAIAfX7kh4A/8jQA...
fsdd-verify-302242
CAALookup not available with standard resolver
Resolved in 197 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), 928 ms total
PASS
1 redirect(s), 928 ms total
Info::
Single redirect
Got: https://nea.org → https://www.nea.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 928 ms total
Got: 928 ms

https://nea.org

370 ms · HTTP/1.1

301

https://www.nea.org/

558 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nea.org301370 msHTTP/1.1cloudflare
2https://www.nea.org/200558 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 3823 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 3823 B Sitemaps referenced 0 User-agents *, Swiftbot 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: *
# 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
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
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
# 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
Disallow: /bill/
Disallow: /professional-excellence/conferences-events/annual-meeting-and-representative-assembly/business-items/
Disallow: /taxonomy/term/

# Give Swiftbot access to Bill nodes. Then, copy all of the rules above to
# ensure that Swiftype is allowed to or is blocked from accessing everything it
# should be allowed to see or blocked from seeing. Some engines (like Google)
# support the grouping of rules for multiple user agents, but it is not a
# standard. See https://developers.google.com/search/docs/advanced/robots/robots_txt#grouping-of-lines-and-rules
User-agent: Swiftbot
Allow: /bill/
# 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
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
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# 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
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
Disallow: /professional-excellence/conferences-events/annual-meeting-and-representative-assembly/business-items/
Disallow: /taxonomy/term/

sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
A+
Domain Intelligence
nea.org — via Network Solutions, LLC, 32 years, 3 months old, hosted on Cloudflare
PASS
nea.org — via Network Solutions, LLC, 32 years, 3 months old, hosted on Cloudflare
Info::
Domain registered until Jun 21, 2027 (1 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: 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: Cloudflare
Got: AS13335
Domain expiry

372 days

June 21, 2027

SSL certificate

70 days

Issued by Let's Encrypt

Domain age

32 years, 3 months

Registered June 22, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.19.251.49

Registrar

Network Solutions, LLC

Unlocked 6 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 Network Solutions, LLC
Created June 22, 1994 (32 years, 3 months ago)
Expires June 21, 2027 (1 years, 2 months)
Last Updated April 23, 2024
Name Servers ns10.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns15.dnsmadeeasy.com
DNSSEC Not enabled
Hosting
IP Address 104.19.251.49
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.5s)

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 435 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 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.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
435 ms
Total Time Total request time from DNS lookup through full response.
435 ms

Connection waterfall

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

Send Feedback