Skip to content
https://nameshift.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
302 Found
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 22 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 22 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

74
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 OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 10 ms lookup
PASS
1 A records, 10 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 199.36.158.100
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-347.awsdns-43.com, ns-909.awsdns-49.net, ns-1044.awsdns-02.org, ns-1745.awsdns-26.co.uk
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: 10 ms
Got: 10 ms
A199.36.158.100
AAAA
CNAME
NSns-347.awsdns-43.com, ns-909.awsdns-49.net, ns-1044.awsdns-02.org, ns-1745.awsdns-26.co.uk
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
hosting-site=nameshift-com
mandrill_verify.QptvGdxYtHo45NLrEYHt7Q
google-site-verification=2Nphv-Ft1K1Bzk-yYr1twU-o9s9BcCrUHsim93kKeSg
stripe-verification=b33c589016c65499ef078143f707476540d0a83bb7ba33b3969b04080b31...
SPF v=spf1 include:servers.mcsv.net include:spf.mandrillapp.com include:_spf.google....
CAALookup not available with standard resolver
Resolved in 10 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), 81 ms total
PASS
1 redirect(s), 81 ms total
Info::
Single redirect
Got: https://nameshift.com → https://nameshift.com/en-gb (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://nameshift.com

https://nameshift.com

41 ms · HTTP/1.1

302

https://nameshift.com/en-gb

40 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nameshift.com30241 msHTTP/1.1Google Frontend
2https://nameshift.com/en-gb20040 msHTTP/1.1

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+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.nameshift.com/
200https://nameshift.com/

Preferred variant: non-www

HTTP → HTTPS

301http://nameshift.com/ https://nameshift.com/

Consistent

A+
Domain Intelligence
nameshift.com — via Hosting Concepts B.V. d/b/a Registrar.eu, 24 years, 6 months old, hosted on Fastly
PASS
nameshift.com — via Hosting Concepts B.V. d/b/a Registrar.eu, 24 years, 6 months old, hosted on Fastly
Info::
Domain registered until Feb 6, 2027 (9 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Hosting Concepts B.V. d/b/a Registrar.eu
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: Fastly
Got: AS54113
Domain expiry

236 days

February 6, 2027

SSL certificate

74 days

Issued by Google Trust Services

Domain age

24 years, 6 months

Registered February 6, 2002

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

199.36.158.100

Registrar

Hosting Concepts B.V. d/b/a Registrar.eu

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Hosting Concepts B.V. d/b/a Registrar.eu
Created February 6, 2002 (24 years, 6 months ago)
Expires February 6, 2027 (9 months)
Last Updated February 6, 2026
Name Servers ns-1044.awsdns-02.org, ns-1745.awsdns-26.co.uk, ns-347.awsdns-43.com, ns-909.awsdns-49.net
DNSSEC Enabled
Hosting
IP Address 199.36.158.100
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 3 ms TCP Connect 0 ms TLS Handshake 5 ms Server Processing 36 ms Content Transfer 0 ms
A
CDN & Delivery
Fastly (MISS)
PASS
Fastly (MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-rtm-ehrd2290032-RTM
Info::
CDN cache status: MISS
CDN Detected: Fastly
Provider Fastly Cache Status MISS Evidence x-served-by: cache-rtm-ehrd2290032-RTM
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback