swagbucks.com is a live website built on Next.js, registered in 2007, served from Frankfurt am Main, Germany. It has a valid HTTPS certificate, 2 of 6 common security headers.
Does swagbucks.com publish the usual trust pages?
Found: privacy. Not found at the usual addresses:
about, contact, terms.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does swagbucks.com compare with other domains analysed here?
Measured against the 74 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 23% of them (median 463ms) |
|---|---|
| Security headers | More than 58% of them |
| Domain age | Older than 53% of them |
Related domains in this index
Analysed domains sharing the same network (AS16509 Amazon.com, Inc.):
- beed.com
- eluniverso.com
- feepayer.com
- honda.com.tr
- ilbianconero.com
- ketua.com
- loans.com.au
- merrickbank.com
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:
- 27b.com
- beenverified.com
- bolia.com
- crunchlabs.com
- drift.com
- emojicombos.com
- fvip.com
- giftcardnest.com
Other analysed domains served from the same country:
When was swagbucks.com registered?
swagbucks.com was registered on 29 October 2007, which makes it about 18 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 MarkMonitor Inc..
Registration runs until 29 October 2027.
The domain carries 3 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 29 October 2007 |
|---|---|
| Expires | 29 October 2027 |
| Registrar | MarkMonitor Inc. |
| Registry status | client delete prohibited, client transfer prohibited, client update prohibited |
Where is swagbucks.com hosted?
The first address resolves to infrastructure in Frankfurt am Main, Germany.
The network is operated by AWS CloudFront (GLOBAL) (AS16509 Amazon.com, 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 swagbucks.com running on?
swagbucks.com exposes 2 identifiable technologies: Next.js, Cloudflare.
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.
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.
- Next.js
- Cloudflare
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 927ms to first byte this response is slow for a homepage measured from a single European location.
The HTML weighs 171KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | nginx/1.31.6 |
|---|---|
| Compression | gzip |
| Page size | 174,957 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The homepage has no title element at all, which leaves search engines to invent one from the page content.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
| Title | — none — (0 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is swagbucks.com served over a valid certificate?
The HTTPS certificate is issued by Amazon and is
valid until 2026-12-08, which is 64 days from the date of this check. It covers
1 hostname.
- swagbucks.com
The certificate has 64 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 (X-Content-Type-Options, Referrer-Policy). Absent: HSTS, Content Security Policy, X-Frame-Options, Permissions-Policy.
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 | yes | nosniff |
| X-Frame-Options | no | — |
| Referrer-Policy | yes | strict-origin-when-cross-origin |
| Permissions-Policy | no | — |
How is DNS configured for swagbucks.com?
| IP addresses | 54.192.35.122, 54.192.35.75, 54.192.35.108, 54.192.35.61 |
|---|---|
| Reverse DNS | server-54-192-35-122.fra56.r.cloudfront.net, server-54-192-35-75.fra56.r.cloudfront.net |
| Name servers | ns-1158.awsdns-16.org, ns-1582.awsdns-05.co.uk, ns-230.awsdns-28.com, ns-749.awsdns-29.net |
| Mail (MX) | aspmx.l.google.com (pri 10), alt1.aspmx.l.google.com (pri 20), alt2.aspmx.l.google.com (pri 20), aspmx2.googlemail.com (pri 30), aspmx3.googlemail.com (pri 30) |
| SPF | v=spf1 ip4:216.225.24.0/24 include:amazonses.com include:_spf.google.com ~all |
| TXT records | 9 |
swagbucks.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 server-54-192-35-122.fra56.r.cloudfront.net, server-54-192-35-75.fra56.r.cloudfront.net, which usually names the hosting provider.
Who runs DNS and mail for swagbucks.com?
DNS is operated by Amazon Route 53 rather than self-hosted name servers.
Mail is handled by Google Workspace.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about swagbucks.com?
3 of 3 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.
Can swagbucks.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.
CAA records restrict certificate issuance to 6 named authorities (issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild sectigo.com, issuewild ssl.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 else does swagbucks.com publish?
A security.txt file is published, giving security researchers a documented way to report vulnerabilities. Very few sites bother.
An ads.txt file is published with 328 entries, which means the site sells programmatic advertising and has declared who may resell its inventory.
An app-ads.txt file is also published, which indicates mobile app inventory alongside the website.
What does robots.txt allow?
robots.txt is 674 bytes and names
4 user-agent groups.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.swagbucks.com/sitemap_index.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 swagbucks.com load from third parties?
The homepage pulls resources from 4 third-party hosts (cdnjs.cloudflare.com, consentmodules.prdgsvc.com, static.cloudflareinsights.com, webexperiments.prdgsvc.com). Each one sees the visitor IP and user agent on every page load.
2 cookies are set before any interaction (AWSALB, AWSALBCORS). 1 lacks the Secure flag.
The page links or refers to X/Twitter, Facebook, Instagram, YouTube.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| AWSALB | no | no | none/unset |
| AWSALBCORS | yes | no | none |
Does swagbucks.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both swagbucks.com and www.swagbucks.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 swagbucks.com be crawled?
A sitemap index is served at https://www.swagbucks.com/sitemap_index.xml listing 4 entries.
The most recent lastmod date is 2026-10-04.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does swagbucks.com run?
No analytics or advertising trackers were detected on the homepage of swagbucks.com, which is unusual for a commercial site.
How does swagbucks.com look when shared?
No Open Graph or Twitter Card tags are present. Links shared to social platforms will fall back to whatever the platform can scrape, usually just a bare URL.
How are images, fonts and scripts handled?
The page pulls 4 external stylesheets and 21 external scripts, with 19 carrying defer or async.
Responses carry Cloudflare edge headers, so content is served from a CDN rather than straight from the origin.
Is swagbucks.com accessible and current?
The page uses 1 landmark element and 0 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index swagbucks.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
Visible text is only 0% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is swagbucks.com delivered?
The HTML is served with Cache-Control: public, max-age=0, must-revalidate.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
A web app manifest is declared, so the site is installable as a progressive web app.
Frequently asked questions
Does swagbucks.com set the usual HTTP security headers?
It sets 2 of 6. The ones not present are: HSTS, Content Security Policy, X-Frame-Options, Permissions-Policy.
Does swagbucks.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 swagbucks.com built with?
The homepage exposes these fingerprints: Next.js, Cloudflare. 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 swagbucks.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 →