Skip to content
https://joins.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
71
GRADE
C
FIX
3
REVIEW
3
PASS
3
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
3 PASS 3 REVIEW 3 FIX
F
Crawlability
Action
robots.txt present, sitemap with 0 URLs
FIX
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 55 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 55 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked
User-agent: *

Disallow: / 

Allow: /$

Allow: /ads.txt
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 404 Expected: 301 redirect to HTTPS

www / non-www

200https://www.joins.com/
200https://joins.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

404http://joins.com/

HTTP version does not redirect to HTTPS

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.

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
HTTP Probe Timing
Total 894 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
280 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
305 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
895 ms
Total Time Total request time from DNS lookup through full response.
895 ms

Connection waterfall

DNS Lookup 29 ms TCP Connect 280 ms TLS Handshake 305 ms Server Processing 281 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
221 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

221
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
1 A records, 28 ms lookup
PASS
1 A records, 28 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 211.218.152.146
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a28-64.akam.net, a26-64.akam.net, a1-127.akam.net, a11-66.akam.net, a12-66.akam.net, a7-64.akam.net
Info::
4 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: 28 ms
Got: 28 ms
A211.218.152.146
AAAA—
CNAME—
NSa28-64.akam.net, a26-64.akam.net, a1-127.akam.net, a11-66.akam.net, a12-66.akam.net, a7-64.akam.net
MX
10 sniper.joins.net
20 sniper2.joins.net
20 sniper2.joongang.co.kr
30 smtpsend.joins.com
TXT
_rpip69zrxz5173ge65xpuxfsli6960f
hibp-verify=dweb_68vsh0gte7if88luqieb78y0
h9cwch0s3qb1nhlmsvnqd3rgptw5k03s
_oawjwon58hnviqvsusv1exg2grql314
SPF v=spf1 include:_spfa.joins.com include:_spfx.joins.com include:_spf.google.com i...
MS=7364DBD508877EECA9148125F80B7AC44F3C3DC5
_l38sfz1bmddoizz4skhxv24s551f1eq
CAALookup not available with standard resolver
Resolved in 28 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://joins.com

https://joins.com

867 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://joins.com200867 msHTTP/1.1Microsoft-IIS/7.5
A+
Domain Intelligence
joins.com — via Whois Corp., 26 years, 9 months old, hosted on KIXS-AS-KR Korea Telecom, KR
PASS
joins.com — via Whois Corp., 26 years, 9 months old, hosted on KIXS-AS-KR Korea Telecom, KR
Info::
Domain registered until Dec 6, 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: Whois Corp.
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: KIXS-AS-KR Korea Telecom, KR
Got: AS4766
Domain expiry

111 days

December 6, 2026

SSL certificate

221 days

Issued by DigiCert Inc

Domain age

26 years, 9 months

Registered December 6, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

KIXS-AS-KR Korea Telecom, KR

ASN AS4766

211.218.152.146

Registrar

Whois Corp.

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 Whois Corp.
Created December 6, 1999 (26 years, 9 months ago)
Expires December 6, 2026 (7 months)
Last Updated June 26, 2025
Name Servers a1-127.akam.net, a11-66.akam.net, a12-66.akam.net, a26-64.akam.net, a28-64.akam.net, a7-64.akam.net
DNSSEC Not enabled
Hosting
IP Address 211.218.152.146
ASN AS4766 (KIXS-AS-KR Korea Telecom, KR)
Provider KIXS-AS-KR Korea Telecom, KR
Data source: rdap (0.3s)

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