Skip to content
https://ntp.org

Infrastructure

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

B
Redirect Chain
1 redirect(s), 4665 ms total
REVIEW
1 redirect(s), 4665 ms total
Info::
Single redirect
Got: https://ntp.org → https://www.ntp.org/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://ntp.org
Warning::
Redirect overhead: 4665 ms total
Got: 4665 ms

https://ntp.org

3056 ms · HTTP/1.1

302

https://www.ntp.org/

1610 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ntp.org3023056 msHTTP/1.1Apache
2https://www.ntp.org/2001610 msHTTP/1.1Apache

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

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.ntp.org/
200https://ntp.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://ntp.org/ → https://www.ntp.org/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 185 ms TCP Connect 179 ms TLS Handshake 371 ms Server Processing 180 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

75
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
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 2005 ms lookup
PASS
2 A records, 2005 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 204.93.207.22, 209.148.110.246
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2001:1838:2000:41b::80:0
Info::
4 nameserver(s) configured
Got: ns1.everett.org, dns2.udel.edu, dns1.udel.edu, anyns.pch.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 (2005 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 2005 ms
A204.93.207.22, 209.148.110.246
AAAA2001:1838:2000:41b::80:0
CNAME—
NSns1.everett.org, dns2.udel.edu, dns1.udel.edu, anyns.pch.net
MX
10 mx0.chi1.ntfo.org
TXT
google-site-verification=1BTIwQr05WxuBXsED2L-cWc-cC7_8NDYKoWMsmAyR3g
google-site-verification=ISMNEfck75SW97AiPz0acClFpICIejjA6F5ijoHccZM
SPF v=spf1 a mx ip4:204.93.207.0/27 ip4:66.220.13.234 ip6:2001:470:1:205::234 ~all
ntp-libera-310
_globalsign-domain-verification=O60kZMoa5mBPIKKqd9FSRXcGUhU6s3rzZHzWNLAlL7
CAALookup not available with standard resolver
Resolved in 2005 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+
IPv6 Readiness
IPv6 reachable (212 ms)
PASS
IPv6 reachable (212 ms)
Info::
IPv6 is configured and reachable at 2001:1838:2000:41b::80:0
Got: 212 ms connect
IPv6 Ready
AAAA Records 2001:1838:2000:41b::80:0 Connection Reachable (212 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 13 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 13 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
ntp.org — via Tucows Domains Inc., 29 years, 8 months old
PASS
ntp.org — via Tucows Domains Inc., 29 years, 8 months old
Info::
Domain registered until Jan 19, 2035 (8 years, 10 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: Tucows 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

3112 days

January 19, 2035

SSL certificate

75 days

Issued by Let's Encrypt

Domain age

29 years, 8 months

Registered January 18, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2001:1838:2000:41b::80:0

Registrar

Tucows Domains Inc.

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 Tucows Domains Inc.
Created January 18, 1997 (29 years, 8 months ago)
Expires January 19, 2035 (8 years, 10 months)
Last Updated March 30, 2025
Name Servers ns1.everett.org, anyns.pch.net, dns1.udel.edu, dns2.udel.edu
DNSSEC Not enabled
Hosting
IP Address 2001:1838:2000:41b::80:0
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