fakaza.com — domain analysis
fakaza.com describes itself as "Fakaza is the right place to discover and download free South African Music, right from Amapiano, gqom, hip hop to afro house music. Visit now to download the latest SA Mp3 songs…". It is built on WordPress, registered in 2016, served from London, United Kingdom. It has a valid HTTPS certificate, 0 of 6 common security headers, 1 tracking script.
What is fakaza.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:
- music ×8
- mellow ×8
- sleazy ×8
- optimist ×6
- album ×6
- news ×5
- kabza ×5
- small ×5
- gifto ×5
- raindrops ×4
Does fakaza.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 fakaza.com compare with other domains analysed here?
Measured against the 81 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 73% of them (median 455ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 37% of them |
Related domains in this index
Analysed domains sharing the same network (AS63949 Akamai Connected Cloud):
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:
- ahrefs.com
- avtub.com
- cottage.com
- clarin.com
- diariopanorama.com.ar
- dropkr.com
- easy.com
- fotomac.com.tr
Other analysed domains served from the same country:
When was fakaza.com registered?
fakaza.com was registered on 17 August 2016, which makes it about 10 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 eNom, LLC.
Registration runs until 17 August 2028.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 17 August 2016 |
|---|---|
| Expires | 17 August 2028 |
| Registrar | eNom, LLC |
| Registry status | client transfer prohibited |
Where is fakaza.com hosted?
The first address resolves to infrastructure in London, United Kingdom.
The network is operated by Linode, LLC (AS63949 Akamai Connected Cloud).
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 fakaza.com running on?
fakaza.com exposes 4 identifiable technologies: WordPress, jQuery, Google Analytics, X-Powered-By: PHP/8.2.34.
WordPress is identifiable from its asset paths, so the platform is public knowledge regardless of whether the version is hidden. That matters mainly for patching discipline: known-platform sites are scanned automatically and constantly.
Visitor tracking is present (Google Analytics), so this homepage is not cookie-free.
- WordPress
- jQuery
- Google Analytics
- X-Powered-By: PHP/8.2.34
The page declares a generator of WordPress 7.1.2.
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 204ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 93KB, which is ordinary for a homepage.
No compression is applied to the HTML. Enabling gzip or brotli usually cuts transfer size by around two thirds at no cost to the server.
| Server header | nginx |
|---|---|
| Compression | none |
| Page size | 95,106 bytes |
| Declared language | en-US |
| Mobile viewport | declared |
What does the homepage say about itself?
The title runs to 70 characters, so search results will truncate it and the end of the sentence will not be read.
The meta description is 186 characters and will be cut short in most result layouts.
No H1 heading was found, so the page offers no single top-level statement of what it is.
All 14 images on the homepage have alt attributes.
| Title | Fakaza: South African Music | Free SA MP3 Download Songs & Videos 2026 (70 chars) |
|---|---|
| Meta description | Fakaza is the right place to discover and download free South African Music, right from Amapiano, gqom, hip hop to afro house music. Visit now to download the latest SA Mp3 songs & more. (186 chars) |
| H1 | — none — (0 on the page) |
| Canonical | https://fakaza.com/ |
| Open Graph title | Fakaza |
| Headings / images | 12 H2s, 14 images (0 without alt text) |
Is fakaza.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-11-09, which is 35 days from the date of this check. It covers
1 hostname.
- fakaza.com
The certificate has 35 days left to run.
It covers 1 hostname, so it was issued for this site specifically.
Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.
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 fakaza.com?
| IP addresses | 178.79.141.21, 2a01:7e00::f03c:94ff:febd:9117 |
|---|---|
| Reverse DNS | 178-79-141-21.ip.linodeusercontent.com, 2a01:7e00::f03c:94ff:febd:9117 |
| Name servers | ns4.linode.com, ns5.linode.com, ns2.linode.com, ns3.linode.com, ns1.linode.com |
| Mail (MX) | mx2.zoho.com (pri 20), mx3.zoho.com (pri 50), mx.zoho.com (pri 10) |
| SPF | v=spf1 include:zoho.com ~all |
| TXT records | 1 |
fakaza.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 3 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 178-79-141-21.ip.linodeusercontent.com, 2a01:7e00::f03c:94ff:febd:9117, which usually names the hosting provider.
Who runs DNS and mail for fakaza.com?
Mail is handled by Zoho Mail.
The domain publishes AAAA records and accepts connections over IPv6.
What else is worth noting about fakaza.com?
11 of 11 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 fakaza.com be spoofed in email?
No DMARC record is published, so there is no instruction telling receiving servers what to do with mail that fails authentication. In practice that means forged mail from this domain is likely to be delivered.
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 else does fakaza.com publish?
An ads.txt file is published with 2688 entries, which means the site sells programmatic advertising and has declared who may resell its inventory.
What does robots.txt allow?
robots.txt is 192 bytes and names
1 user-agent group.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://fakaza.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?
- Organization
- PostalAddress
- ContactPoint
- CollectionPage
- BreadcrumbList
- ListItem
- WebSite
- SearchAction
- EntryPoint
- PropertyValueSpecification
- ImageObject
The homepage publishes 11 structured data types: Organization, PostalAddress, ContactPoint, CollectionPage, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, ImageObject.
What does fakaza.com load from third parties?
The homepage pulls resources from 4 third-party hosts (d5nxst8fruw4z.cloudfront.net, facebook.com, googletagmanager.com, platform.twitter.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, Facebook, Instagram.
Does fakaza.com settle on one address?
Plain HTTP serves the site directly instead of redirecting to HTTPS. That leaves an unencrypted copy reachable and gives search engines two addresses for the same content.
The www hostname does not respond at all, so anyone typing www.fakaza.com reaches nothing.
How easily can fakaza.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL returns HTTP 200 rather than 404. That is a soft 404: every mistyped or stale link becomes an indexable page, which inflates the site with duplicates.
What tracking does fakaza.com run?
1 tracking script detected: Google Analytics.
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 fakaza.com look when shared?
4 of 5 social preview tags are set. Missing: og:image.
How are images, fonts and scripts handled?
14 images on the homepage, 8 of them lazy-loaded (57%).
Modern image formats are in use (21 WebP/AVIF references).
No srcset attributes are used, so every device is served the same image size regardless of screen.
Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.
The page pulls 3 external stylesheets and 13 external scripts, with 6 carrying defer or async.
No preconnect hints are declared despite third-party scripts being present, so each new origin pays a full connection setup before it can deliver anything.
Is fakaza.com accessible and current?
The page uses 2 landmark elements and 1 ARIA attribute.
The viewport tag disables pinch-zoom. That fails WCAG 1.4.4 and is a genuine problem for anyone who needs to enlarge text.
There are 4 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.
The visible copyright notice reads 2016, 10 years behind the current year, which usually indicates the site is not actively maintained.
Can search engines index fakaza.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 121 internal and 1 external link across 1 outside host.
Visible text is only 3.4% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is fakaza.com delivered?
No Cache-Control header is sent for the HTML, so caching behaviour is left to browser defaults.
Frequently asked questions
Does fakaza.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 fakaza.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 fakaza.com built with?
The homepage exposes these fingerprints: WordPress, jQuery, Google Analytics, X-Powered-By: PHP/8.2.34. 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 fakaza.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 →