✓ Independen — bukan situs pemerintah ✓ Setiap langkah dicocokkan dengan portal resmi ✓ Kami tidak pernah meminta NIK, OTP, atau kata sandi Anda

contentrewards.com — domain analysis

contentrewards.com describes itself as "Content Rewards is where brands pay creators for the views their content earns. Launch a campaign, or start clipping and get paid per 1K views.". It is built on Next.js, registered in 2014, served from Atlanta, United States. It has a valid HTTPS certificate, 0 of 6 common security headers, 1 tracking script.

Searched as: “content rewards .com”.

200HTTP status
56msResponse time
658Words on the homepage
0/6Security headers set

What is contentrewards.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:

  • campaign ×10
  • creators ×8
  • rewards ×7
  • views ×6
  • platform ×5
  • campaigns ×5
  • post ×5
  • payout ×5
  • content ×4
  • budget ×4

Does contentrewards.com publish the usual trust pages?

All four of the pages a established business normally publishes were found:
about, contact, privacy and terms.

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

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

Measured against the 463 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 92% of them
(median 453ms)
Security headers More than 0% of them
Domain age Older than 36% of them

Related domains in this index

Analysed domains built on a similar stack:

Other analysed domains served from the same country:

When was contentrewards.com registered?

contentrewards.com was registered on 7 October 2014, which makes it about 12 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 Domain.com – Network Solutions, LLC.

Registration runs until 7 October 2027.

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

Registered 7 October 2014
Expires 7 October 2027
Registrar Domain.com – Network Solutions, LLC
Registry status client transfer prohibited

Where is contentrewards.com hosted?

The first address resolves to infrastructure in Atlanta, United States.

The network is operated by AWS CloudFront (GLOBAL).

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 contentrewards.com running on?

contentrewards.com exposes 3 identifiable technologies: Next.js, Google Tag Manager, X-Powered-By: Next.js.

The build output indicates a server-rendered JavaScript framework, which means the HTML served to crawlers is generated ahead of time rather than assembled in the browser.

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

  • Next.js
  • Google Tag Manager
  • X-Powered-By: Next.js

How does the homepage respond?

The server answered with HTTP 200 over
HTTPS.

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

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

The HTML is compressed with gzip.

Server header not disclosed
Compression gzip
Page size 257,216 bytes
Declared language en
Mobile viewport declared

What does the homepage say about itself?

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

A meta description of 143 characters is present.

All 68 images on the homepage have alt attributes.

Title Content Rewards | Clipping & UGC Campaign Platform (50 chars)
Meta description Content Rewards is where brands pay creators for the views their content earns. Launch a campaign, or start clipping and get paid per 1K views. (143 chars)
H1 The Marketplace for Virality (1 on the page)
Canonical https://contentrewards.com
Open Graph title Content Rewards | Clipping & UGC Campaign Platform
Headings / images 8 H2s, 68 images (0 without alt text)

Is contentrewards.com served over a valid certificate?

The HTTPS certificate is issued by Amazon and is
valid until 2027-03-14, which is 116 days from the date of this check. It covers
2 hostnames.

  • *.contentrewards.com
  • contentrewards.com

The certificate has 116 days left to run.

It covers 2 hostnames, so it was issued for this site specifically.

Which security headers does it set?

None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.

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

With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.

Header Set Value
HSTS no —
Content Security Policy no —
X-Content-Type-Options no —
X-Frame-Options no —
Referrer-Policy no —
Permissions-Policy no —

How is DNS configured for contentrewards.com?

IP addresses 18.155.0.46, 18.155.0.129, 18.155.0.26, 18.155.0.20, 2600:9000:2102:3600:13:8620:5e00:93a1, 2600:9000:2102:ba00:13:8620:5e00:93a1, 2600:9000:2102:f800:13:8620:5e00:93a1, 2600:9000:2102:9000:13:8620:5e00:93a1, 2600:9000:2102:fa00:13:8620:5e00:93a1, 2600:9000:2102:b600:13:8620:5e00:93a1, 2600:9000:2102:b000:13:8620:5e00:93a1, 2600:9000:2102:ac00:13:8620:5e00:93a1
Reverse DNS server-18-155-0-46.fra60.r.cloudfront.net, server-18-155-0-129.fra60.r.cloudfront.net
Name servers simon.ns.cloudflare.com, holly.ns.cloudflare.com
Mail (MX) smtp.google.com (pri 1)
SPF v=spf1 ip4:66.96.128.0/18 include:_spf.google.com include:websitewelcome.com ~all
TXT records 5

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

Mail is handled by 1 exchanger.

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

Reverse DNS resolves to server-18-155-0-46.fra60.r.cloudfront.net, server-18-155-0-129.fra60.r.cloudfront.net, which usually names the hosting provider.

Who runs DNS and mail for contentrewards.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 contentrewards.com?

32 of 32 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.

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

The server discloses software detail in x-powered-by, which tells an attacker what to target without them having to probe for it.

Can contentrewards.com be spoofed in email?

DMARC is set to quarantine, so mail failing authentication is sent to spam rather than the inbox.

CAA records restrict certificate issuance to 6 named authorities (issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild amazonaws.com), so no other CA should be able to issue 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 590 bytes and names
1 user-agent group.

It does not blanket-disallow general crawlers.

Sitemaps declared:

  • https://contentrewards.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?

  • Organization
  • PostalAddress
  • ContactPoint
  • ImageObject
  • WebSite

The homepage publishes 5 structured data types: Organization, PostalAddress, ContactPoint, ImageObject, WebSite.

What does contentrewards.com load from third parties?

The homepage pulls resources from 4 third-party hosts (analytics.ahrefs.com, cdn.sanity.io, crusercontent.com, images.unsplash.com). Each one sees the visitor IP and user agent on every page load.

No cookies are set on first load.

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

Does contentrewards.com settle on one address?

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

The www address redirects to https://contentrewards.com/, so the site settles on one canonical hostname.

How easily can contentrewards.com be crawled?

A sitemap is served at https://contentrewards.com/sitemap.xml listing 925 entries.

The most recent lastmod date is 2026-11-18.

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

What tracking does contentrewards.com run?

1 tracking script detected: Google Tag Manager.

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 contentrewards.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?

68 images on the homepage, 45 of them lazy-loaded (66%).

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

The page pulls 5 external stylesheets and 32 external scripts, with 33 carrying defer or async.

Responses carry Amazon CloudFront and edge cache edge headers, so content is served from a CDN rather than straight from the origin.

Is contentrewards.com accessible and current?

The page uses 7 landmark elements and 128 ARIA attributes.

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

No skip-to-content link was found, which keyboard users rely on to bypass navigation.

Can search engines index contentrewards.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 22 internal and 7 external links across 6 outside hosts.

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

How is contentrewards.com delivered?

The HTML is served with Cache-Control: s-maxage=31536000.

A web app manifest is declared, so the site is installable as a progressive web app.

Frequently asked questions

What is content rewards .com?

People who search for “content rewards .com” are looking for the website at contentrewards.com. contentrewards.com describes itself as "Content Rewards is where brands pay creators for the views their content earns. Launch a campaign, or start clipping and get paid per 1K views.". It is built on Next.js, registered in 2014, served from Atlanta, United States. It has a valid HTTPS certificate, 0 of 6 common security headers, 1 tracking script.

Does contentrewards.com set the usual HTTP security headers?

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

Does contentrewards.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 contentrewards.com built with?

The homepage exposes these fingerprints: Next.js, Google Tag Manager, X-Powered-By: Next.js. 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 18 November 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 contentrewards.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 18 November 2026.
Analyse another domain →

⚠ Tetap waspada

Urus adalah panduan independen, bukan situs pemerintah. Lakukan prosesnya hanya di portal resmi. Tidak ada instansi resmi yang meminta OTP, NIK, kata sandi, atau PIN Anda lewat telepon, pesan, atau "bantuan" — jangan pernah memberikannya.

Urus adalah panduan independen dan tidak berafiliasi dengan instansi pemerintah mana pun. Biaya, tautan, dan langkah dapat berubah — selalu konfirmasi di portal resmi sebelum bertindak. Ini informasi umum, bukan nasihat hukum atau keuangan.