jsonapi.org
jsonapi.org is a live website, registered in 2013, served from San Francisco, United States. It has a valid HTTPS certificate, 0 of 6 common security headers, 1 tracking script.
What is jsonapi.org 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:
- json ×16
- example ×12
- http ×11
- type ×11
- articles ×10
- comments ×10
- links ×9
- self ×7
- specification ×6
- author ×6
Does jsonapi.org 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 jsonapi.org compare with other domains analysed here?
Measured against the 121 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 93% of them (median 790ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 88% of them |
Related domains in this index
Analysed domains built on a similar stack:
- theinstanavigation.com
- quikconsole.com
- aavot.com
- apkbros.com
- bettingages.com
- cbpng.com
- coatnews.com
- cookiesforlove.com
Other analysed domains served from the same country:
- stackoverflow.com
- vercel.com
- mozilla.org
- kextra.com
- tiktokkio.com
- feedbackmagazines.org
- thealite.com.au
When was jsonapi.org registered?
jsonapi.org was registered on 30 April 2013, which makes it about 13 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 Amazon Registrar, Inc..
Registration runs until 30 April 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 30 April 2013 |
|---|---|
| Expires | 30 April 2027 |
| Registrar | Amazon Registrar, Inc. |
| Registry status | client transfer prohibited |
Where is jsonapi.org hosted?
The first address resolves to infrastructure in San Francisco, United States.
The network is operated by GitHub, Inc (AS54113 Fastly, 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 jsonapi.org running on?
jsonapi.org exposes 2 identifiable technologies: jQuery, Google Analytics.
Visitor tracking is present (Google Analytics), so this homepage is not cookie-free.
- jQuery
- Google Analytics
How does the homepage respond?
The server answered with HTTP 200 over HTTPS.
At 66ms to first byte this response is fast for a homepage measured from a single European location.
The HTML weighs 19KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | GitHub.com |
|---|---|
| Compression | gzip |
| Page size | 18,983 bytes |
| Declared language | not declared |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 52 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 1 images on the homepage have alt attributes.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | JSON:API — A specification for building APIs in JSON (52 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | JSON:API (1 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 5 H2s, 1 images (0 without alt text) |
Is jsonapi.org served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is valid until 2026-11-16, which is 43 days from the date of this check. It covers 2 hostnames.
- jsonapi.org
- www.jsonapi.org
The certificate has 43 days left to run.
It covers 2 hostnames, 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 jsonapi.org?
| IP addresses | 185.199.108.153, 185.199.111.153, 185.199.110.153, 185.199.109.153 |
|---|---|
| Reverse DNS | cdn-185-199-108-153.github.com, cdn-185-199-111-153.github.com |
| Name servers | ns-1168.awsdns-18.org, ns-1985.awsdns-56.co.uk, ns-505.awsdns-63.com, ns-865.awsdns-44.net |
| Mail (MX) | no mail records |
| SPF | v=spf1 include:_hostedspf.discourse.org ~all |
| TXT records | 1 |
jsonapi.org resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
No MX records are published, so this domain does not receive mail at its apex. Mail sent to it will bounce.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to cdn-185-199-108-153.github.com, cdn-185-199-111-153.github.com, which usually names the hosting provider.
Who runs DNS and mail for jsonapi.org?
DNS is operated by Amazon Route 53 rather than self-hosted name servers.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about jsonapi.org?
1 of 1 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.
What has changed on jsonapi.org?
This domain has been checked 2 times. Only checks where something actually moved are recorded, so each row below is a real change rather than a repeat measurement.
| Checked | HTTP | Response | IP | Headers |
|---|---|---|---|---|
| 4 Oct 2026 | 200 | 66ms | 185.199.108.153 | 0/6 |
| 4 Oct 2026 | 200 | 212ms | 185.199.109.153 | 0/6 |
Changes recorded at the most recent check:
- IP address: 185.199.109.153 → 185.199.108.153
- name servers: ns-865.awsdns-44.net,ns-1168.awsdns-18.org,ns-1985.awsdns-56.co.uk,ns-505.awsdns-63.com → ns-1168.awsdns-18.org,ns-1985.awsdns-56.co.uk,ns-505.awsdns-63.com,ns-865.awsdns-44.net
Can jsonapi.org 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 does robots.txt allow?
No robots.txt was served. Crawlers treat a missing file as permission to crawl everything, so this is an open crawl policy by default rather than a blocked one.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does jsonapi.org load from third parties?
The homepage pulls resources from 2 third-party hosts (ajax.googleapis.com, licensebuttons.net). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
3 resources are referenced over plain HTTP on an HTTPS page, which browsers block or flag as mixed content.
The page links or refers to X/Twitter, GitHub.
Does jsonapi.org 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://jsonapi.org/, so the site settles on one canonical hostname.
How easily can jsonapi.org be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does jsonapi.org 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 jsonapi.org 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?
1 image on the homepage, 0 of them lazy-loaded (0%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 3 external stylesheets and 3 external scripts, with 0 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.
Responses carry Fastly and Varnish/Fastly edge and edge cache edge headers, so content is served from a CDN rather than straight from the origin.
Is jsonapi.org accessible and current?
The page uses 4 landmark elements and 0 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index jsonapi.org?
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.
The homepage carries 16 internal and 9 external links across 7 outside hosts.
Visible text makes up 18.4% of the HTML.
How is jsonapi.org delivered?
The HTML is served with Cache-Control: max-age=600.
A web app manifest is declared, so the site is installable as a progressive web app.
The TLS certificate also covers 1 subdomain: www.jsonapi.org.
- www.jsonapi.org
Frequently asked questions
Does jsonapi.org 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 jsonapi.org allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
What is jsonapi.org built with?
The homepage exposes these fingerprints: jQuery, Google Analytics. 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 4 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 jsonapi.org and want this page removed.
Email hello@quikconsolecom.net from an address at the domain and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026. Analyse another domain →