Skip to content

jim.com — domain analysis

TweetSharePinShare0 Shares jim.com is a live website built on Webflow, registered in 1995, served from Toronto, Canada. It has a valid HTTPS certificate, 2 of 6 common security…

1 min read
Share Facebook X Pinterest WhatsApp
Tweet
Share
Pin
Share
0 Shares

jim.com is a live website built on Webflow, registered in 1995, served from Toronto, Canada. It has a valid HTTPS certificate, 2 of 6 common security headers, 2 tracking scripts.

200HTTP status
1230msResponse time
1,146Words on the homepage
2/6Security headers set

What is jim.com about?

The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:

  • card ×14
  • payment ×12
  • using ×8
  • business ×8
  • paid ×7
  • funds ×7
  • bank ×7
  • fees ×6
  • contactless ×5
  • payments ×5

Does jim.com publish the usual trust pages?

Found: about. Not found at the usual addresses:
contact, privacy, terms.

These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.

How does jim.com compare with other domains analysed here?

Measured against the 76 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.

Response time Faster than 16% of them
(median 443ms)
Security headers More than 60% of them
Domain age Older than 86% of them

Related domains in this index

Analysed domains sharing the same network (AS13335 Cloudflare, Inc.):

Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.

Analysed domains built on a similar stack:

Other analysed domains served from the same country:

When was jim.com registered?

jim.com was registered on 24 February 1995, which makes it about 31 years old.

A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.

The registrar of record is NameCheap, Inc..

Registration runs until 25 February 2030.

The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.

Registered 24 February 1995
Expires 25 February 2030
Registrar NameCheap, Inc.
Registry status client transfer prohibited

Where is jim.com hosted?

The first address resolves to infrastructure in Toronto, Canada.

The network is operated by Cloudflare, Inc. (AS13335 Cloudflare, Inc.).

Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.

What is jim.com running on?

jim.com exposes 3 identifiable technologies: Webflow, Cloudflare, Google Tag Manager.

Cloudflare sits in front of the origin, so the server header, IP addresses and response timing describe the edge rather than the machine actually running the site.

Visitor tracking is present (Google Tag Manager), so this homepage is not cookie-free.

  • Webflow
  • Cloudflare
  • Google Tag Manager

How does the homepage respond?

The server answered with HTTP 200 over
HTTPS.

At 1230ms to first byte this response is slow for a homepage measured from a single European location.

The HTML weighs 418KB, which is ordinary for a homepage.

The HTML is compressed with gzip.

Server header cloudflare
Compression gzip
Page size 428,049 bytes
Declared language en
Mobile viewport declared

What does the homepage say about itself?

The title is 55 characters, inside the range that displays without truncation.

There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.

All 58 images on the homepage have alt attributes.

Title Jim | Your AI Hire That Gets You Paid — Instant Payouts (55 chars)
Meta description — none — (0 chars)
H1 Sell anywhere. Get paid instantly. (1 on the page)
Canonical https://www.jim.com/
Open Graph title not set
Headings / images 9 H2s, 58 images (0 without alt text)

Is jim.com served over a valid certificate?

The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-12-12, which is 68 days from the date of this check. It covers
1 hostname.

  • jim.com

The certificate has 68 days left to run.

It covers 1 hostname, so it was issued for this site specifically.

Which security headers does it set?

2 of 6 are set (Content Security Policy, X-Frame-Options). Absent: HSTS, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.

Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.

Header Set Value
HSTS no —
Content Security Policy yes frame-ancestors 'self'
X-Content-Type-Options no —
X-Frame-Options yes SAMEORIGIN
Referrer-Policy no —
Permissions-Policy no —

How is DNS configured for jim.com?

IP addresses 104.18.19.9, 104.18.18.9, 2606:4700::6812:1309, 2606:4700::6812:1209
Reverse DNS 104.18.19.9, 104.18.18.9
Name servers lorna.ns.cloudflare.com, doug.ns.cloudflare.com
Mail (MX) aspmx.l.google.com (pri 1), alt3.aspmx.l.google.com (pri 10), alt4.aspmx.l.google.com (pri 10), alt1.aspmx.l.google.com (pri 5), alt2.aspmx.l.google.com (pri 5)
SPF v=spf1 include:_spf.google.com ~all
TXT records 3

jim.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.

Mail is handled by 5 exchangers.

An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.

Reverse DNS resolves to 104.18.19.9, 104.18.18.9, which usually names the hosting provider.

Who runs DNS and mail for jim.com?

DNS is operated by Cloudflare rather than self-hosted name servers.

Mail is handled by Google Workspace.

The domain publishes AAAA records and accepts connections over IPv6.

What else is worth noting about jim.com?

12 of 16 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.

4 email addresses appear in the homepage markup, where address-harvesting crawlers will find them.

Can jim.com be spoofed in email?

DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.

No CAA records are published, so any certificate authority may issue a certificate for this domain.

The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.

What does robots.txt allow?

robots.txt is 122 bytes and names
1 user-agent group.

It does not blanket-disallow general crawlers.

Sitemaps declared:

  • https://www.jim.com/sitemap.xml

AI crawler policy

robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.

What structured data does the homepage publish?

No JSON-LD or microdata was found on the homepage.

What does jim.com load from third parties?

The homepage pulls resources from 7 third-party hosts (cdn.jsdelivr.net, cdn.prod.website-files.com, cdn.rudderlabs.com, d3e54v103j8qbb.cloudfront.net, googletagmanager.com, jimussagosqd.dataplane.rudderstack.com). Each one sees the visitor IP and user agent on every page load.

1 cookie is set before any interaction (exp_device_id).

The page links or refers to X/Twitter, LinkedIn, Facebook, Instagram, YouTube.

Cookie Secure HttpOnly SameSite
exp_device_id yes no lax

Does jim.com settle on one address?

Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.

Both jim.com and www.jim.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.

How easily can jim.com be crawled?

A sitemap is served at https://www.jim.com/sitemap.xml listing 442 entries.

The most recent lastmod date is 2026-09-30.

A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.

What tracking does jim.com run?

2 tracking scripts detected: Google Tag Manager, Microsoft Clarity.

No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.

How does jim.com look when shared?

All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.

How are images, fonts and scripts handled?

58 images on the homepage, 53 of them lazy-loaded (91%).

Modern image formats are in use (76 WebP/AVIF references).

The page pulls 2 external stylesheets and 17 external scripts, with 2 carrying defer or async.

Responses carry Cloudflare edge headers, so content is served from a CDN rather than straight from the origin.

Is jim.com accessible and current?

The page uses 18 landmark elements and 69 ARIA attributes.

There are 3 form inputs but only 2 label elements, so some fields may be unlabelled for screen readers.

Can search engines index jim.com?

Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.

The homepage carries 79 internal and 5 external links across 5 outside hosts.

Visible text is only 1.7% of the HTML, which indicates the page is assembled in the browser rather than served as content.

How is jim.com delivered?

No Cache-Control header is sent for the HTML, so caching behaviour is left to browser defaults.

Frequently asked questions

Does jim.com set the usual HTTP security headers?

It sets 2 of 6. The ones not present are: HSTS, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.

Does jim.com allow AI crawlers?

robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.

What is jim.com built with?

The homepage exposes these fingerprints: Webflow, Cloudflare, Google Tag Manager. A site behind a CDN or rendered server-side may use more than it reveals.

Where does this data come from?

Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.

Is any of this traffic or authority data?

No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.

I own jim.com and want this page removed.

Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.

Analysed 5 October 2026.
Analyse another domain →

Tweet
Share
Pin
Share
0 Shares

You Might Also Like

Newsletter

Get the Buzz First

Celebrity and influencer news straight to your inbox — no spam, just the good stuff.

Get the daily celebrity buzz in your inbox.

Join thousands who never miss a headline. Unsubscribe any time.