Skip to content
https://nifty.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
1
REVIEW
6
PASS
2
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
2 PASS 6 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), 2174 ms total
REVIEW
1 redirect(s), 2174 ms total
Info::
Single redirect
Got: https://nifty.com → https://www.nifty.com:443/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2174 ms total
Got: 2174 ms

https://nifty.com

885 ms · HTTP/1.1

301

https://www.nifty.com:443/

1288 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nifty.com301885 msHTTP/1.1
2https://www.nifty.com:443/2001288 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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: 93 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 93 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent:*

Disallow:/hpr/

Disallow:/cgi-bin/go

Disallow:/iw/

Disallow:/navi/birthday/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.nifty.com/
200https://nifty.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nifty.com/ → https://www.nifty.com:443/

Consistent

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

Connection waterfall

DNS Lookup 253 ms TCP Connect 1 ms TLS Handshake 433 ms Server Processing 216 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
184 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

184
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
2 A records, 708 ms lookup
PASS
2 A records, 708 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 76.223.106.131, 75.2.109.238
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: odns0.nifty.ad.jp, odns2.nifty.ad.jp, odns1.nifty.ad.jp
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 (708 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 708 ms
A76.223.106.131, 75.2.109.238
AAAA—
CNAME—
NSodns0.nifty.ad.jp, odns2.nifty.ad.jp, odns1.nifty.ad.jp
MX
10 mx2.nifty.com
TXT
google-site-verification=KiXiyOAC7zoylK_N-vmVqLJmY2um1kHJaX5rGKS0hN4
amazonses:nFpQ+iAcVdp3M2k8zO2PwIHHTSjRXF+0O2kfRpJ7Mow=
amazonses:4Mrusw3/TJpXnU7irQ3zMR95XR0tR523krDFhzlPv1A=
google-site-verification=ezSKxSA1s-PIl5RlBNDiMGoOEkBOR1fBLfNCdh-lfoU
amazonses:/Alan0ux6gDkyvsSJJHLEa4vsS6g5Xi8qeDoXqOKrxI=
amazonses:AgLuT5ebNqSd2VBOj5sGCKxGa8Z0cwxwNMiabIO6mp8=
amazonses:RRh4iVzSCRb3ITrbbu8V46UQdPSwH3CCbn1dnlNwhZY=
uCpabknftnCQtbkinUN4Hf7Y6wtzZo
amazonses:CgfSxQANS31ZqzUKWFgdv349cU2HgbOsTJmdLOXG29E=
amazonses:hf8y8vy4CAlr66Rw7MdE/oyteayP3SMPcf4RDCI1d2A=
amazonses:LBQr5qJRUcyIqPw5ahJ3HBOw4vxdQeutrSUHnOLXYVU=
amazonses:0QGA5rdeHo3NPrL3ycYJP5VukcFE8YK2HJLfGYZU2wo=
SPF v=spf1 include:spf-03.nifty.com include:spf-04.nifty.com include:spf.ess.nifclou...
amazonses:xRgjqp3xaQ3BnO68RIh2Pzt2L+d/RRAuk9U8gNd9ZvM=
CAALookup not available with standard resolver
Resolved in 708 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+
Domain Intelligence
nifty.com — via Japan Registry Services Co., Ltd., 27 years, 11 months old, hosted on AWS
PASS
nifty.com — via Japan Registry Services Co., Ltd., 27 years, 11 months old, hosted on AWS
Info::
Domain registered until Oct 7, 2026 (5 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: Japan Registry Services Co., Ltd.
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: AWS
Got: AS16509
Domain expiry

82 days

October 7, 2026

SSL certificate

184 days

Issued by Amazon

Domain age

27 years, 11 months

Registered October 8, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

75.2.109.238

Registrar

Japan Registry Services Co., Ltd.

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Japan Registry Services Co., Ltd.
Created October 8, 1998 (27 years, 11 months ago)
Expires October 7, 2026 (5 months)
Last Updated February 17, 2026
Name Servers odns0.nifty.ad.jp, odns1.nifty.ad.jp, odns2.nifty.ad.jp
DNSSEC Not enabled
Hosting
IP Address 75.2.109.238
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.9s)

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