loket.com describes itself as "Beli tiket konser, festival, sport event, dan event seru lainnya dengan mudah di LOKET. #PASTIBISA beli tiket event idaman!". It was registered in 2003, served from Toronto, Canada. It has a valid HTTPS certificate, 4 of 6 common security headers.

200HTTP status
638msResponse time
10Words on the homepage
4/6Security headers set

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

  • tiket ×2

Does loket.com publish the usual trust pages?

None of about, contact, privacy or terms could be found at their usual addresses.
That is common for small or single-purpose sites, and it is also what a disposable
site looks like, so it is worth noting rather than concluding from.

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

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

Measured against the 77 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 39% of them
(median 496ms)
Security headers More than 76% of them
Domain age Older than 60% 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 loket.com registered?

loket.com was registered on 27 May 2003, which makes it about 23 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 GoDaddy.com, LLC.

Registration runs until 27 May 2027.

The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.

Registered 27 May 2003
Expires 27 May 2027
Registrar GoDaddy.com, LLC
Registry status client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited

Where is loket.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 loket.com running on?

loket.com exposes 1 identifiable technology: Cloudflare.

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.

  • Cloudflare

How does the homepage respond?

The server answered with HTTP 200 over
HTTPS.

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

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

The HTML is compressed with gzip.

Server header cloudflare
Compression gzip
Page size 98,015 bytes
Declared language id-ID
Mobile viewport declared

What does the homepage say about itself?

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

A meta description of 123 characters is present.

No H1 heading was found, so the page offers no single top-level statement of what it is.

Title LOKET: Beli Tiket Event & Tiket Konser Mudah dan Terpercaya (59 chars)
Meta description Beli tiket konser, festival, sport event, dan event seru lainnya dengan mudah di LOKET. #PASTIBISA beli tiket event idaman! (123 chars)
H1 — none — (0 on the page)
Canonical https://loket.com
Open Graph title LOKET: Beli Tiket Event & Tiket Konser Mudah dan Terpercaya
Headings / images 0 H2s, 0 images (0 without alt text)

Is loket.com served over a valid certificate?

The HTTPS certificate is issued by Sectigo Limited and is
valid until 2026-10-30, which is 25 days from the date of this check. It covers
2 hostnames.

  • *.loket.com
  • loket.com

The certificate has 25 days left to run.

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

Which security headers does it set?

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

Header Set Value
HSTS yes max-age=16000000; includeSubDomains; preload;
Content Security Policy yes default-src * 'unsafe-inline' 'unsafe-eval' data: blob:; frame-ancestors 'self' *.loket.com *.loket.id;
X-Content-Type-Options yes nosniff
X-Frame-Options no —
Referrer-Policy yes strict-origin
Permissions-Policy no —

How is DNS configured for loket.com?

IP addresses 172.66.157.87, 104.20.26.108, 2606:4700:10::ac42:9d57, 2606:4700:10::6814:1a6c
Reverse DNS 172.66.157.87, 104.20.26.108
Name servers ned.ns.cloudflare.com, irma.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 include:mailgun.org include:amazonses.com ~all
TXT records 7

loket.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 172.66.157.87, 104.20.26.108, which usually names the hosting provider.

Who runs DNS and mail for loket.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 loket.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.

Can loket.com be spoofed in email?

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

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 loket.com publish?

An ads.txt file is published with 1 entries, which means the site sells programmatic advertising and has declared who may resell its inventory.

What does robots.txt allow?

robots.txt is 501 bytes and names
12 user-agent groups.

It does not blanket-disallow general crawlers.

No sitemap is declared in robots.txt.

AI crawler policy

Crawler Policy
gptbot blocked
claudebot blocked
google-extended blocked
ccbot blocked
applebot-extended blocked
bytespider blocked
anthropic-ai blocked

No sitemap is declared in robots.txt, so crawlers must discover pages by following links.

Every named AI crawler is blocked (gptbot, claudebot, google-extended, ccbot, applebot-extended, bytespider, anthropic-ai). This domain has opted out of AI training and AI answer surfaces wholesale.

What structured data does the homepage publish?

  • ItemList
  • ListItem

The homepage publishes 2 structured data types: ItemList, ListItem.

What does loket.com load from third parties?

The homepage loads no resources from third-party hosts at all, which is rare and means visiting it tells no other company that you did.

No cookies are set on first load.

Does loket.com settle on one address?

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

Both loket.com and www.loket.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 loket.com 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 loket.com run?

No analytics or advertising trackers were detected on the homepage of loket.com, which is unusual for a commercial site.

How does loket.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?

The page pulls 0 external stylesheets and 3 external scripts, with 0 carrying defer or async.

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

Is loket.com accessible and current?

The page uses 0 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 loket.com?

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

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

How is loket.com delivered?

The HTML is served with Cache-Control: max-age=1.

Frequently asked questions

Does loket.com set the usual HTTP security headers?

It sets 4 of 6. The ones not present are: X-Frame-Options, Permissions-Policy.

Does loket.com allow AI crawlers?

No — robots.txt blocks gptbot, claudebot, google-extended, ccbot, applebot-extended, bytespider, anthropic-ai.

What is loket.com built with?

The homepage exposes these fingerprints: 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 loket.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 →