Is xl.co.id down or not working?

What happened to xl.co.id, why did the website go down and not work? Here you can see who else is having the same problem with xl.co.id, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, xl.co.id is working fine, but single failures are possible. If xl.co.id does not work for you, then report your problem and write a comment.

What to do if the site xl.co.id is not available? Try our guide.

xl.co.id outage reports in the last 24 hours

xl.co.id - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Protocol:
https
Status code:
200
Page size:
34.1 KB
Response time:
1.336sec.
IP:
99.83.183.23
Response headers:
date: Fri, 04 Oct 2024 08:19:52 GMT
content-type: text/html; charset=utf-8
transfer-encoding: chunked
connection: close
set-cookie: stickounet=1728029993.157.27.392366|4976afcb93dcf4e6b62bab8d6283a548; Expires=Sun, 06-Oct-24 08:19:52 GMT; Max-Age=172800; Path=/; HttpOnly,__cf_bm=drC3bbHk980N1hzedJk7DKcHTr6igvI7toCcNRdXbug-1728029992-1.0.1.1-zF6f6auf0WPBTc3OiYouNgG35zlYgQdzq4xTlp1BOJw7kiebH3F03gIN8Sw6R8hFtRGo5b69VsO0tl8oSDETlg; path=/; expires=Fri, 04-Oct-24 08:49:52 GMT; domain=.xl.co.id; HttpOnly; Secure; SameSite=None
x-dns-prefetch-control: on
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
referrer-policy: origin-when-cross-origin
permissions-policy: camera=(), microphone=(), geolocation=(), interest-cohort=()
strict-transport-security: max-age=31536000
content-security-policy: frame-ancestors 'none';
x-powered-by: Next.js
cache-control: s-maxage=60, stale-while-revalidate
vary: Accept-Encoding
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 8cd3bfd88a210eb2-AMS
DNS records:
A address99.83.183.23
ttl21600
A address75.2.123.169
ttl21600
AAAA address2400:9800:0:220::1
ttl21600
MX exchangemail2.xl.co.id
priority10
MX exchangemail1.xl.co.id
priority10
MX exchangemail3.xl.co.id
priority50
MX exchangemail4.xl.co.id
priority50
NS valuesocrates.xl.net.id
NS valuesnbdc-dns1.xl.net.id
NS valuehertz.xl.net.id
NS valueavicenna.xl.co.id
NS valueplato.xl.co.id
NS valuesnbdc-dns2.xl.net.id
TXT entriesv=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
TXT entriesgoogle-site-verification=a_w51nfi_raWPdxj9Dq4GrtX5kQ5MQKQjFP2xr1yTFo
TXT entriesgoogle-site-verification=2PDovYTtbrxaFzyQBBEcjUB1SH5cAYypCAerzI5kPRc
TXT entriesQjv+lcrXdOUup36PCtIXSN/sOX+bdqKW6xcxBkE1wBJyxQ8DgtyjVY+jeyzsyMYlHF5HDR085mT4YBsPzZfgQg==
TXT entriesMS=ms58499430
TXT entriesyahoo-verification-key=z4g2D/gEpUAMrCi5EYdm58Txj3ALvNz9tqt2ABzxzU8=
SOA nsnamesocrates.xl.net.id
hostmasterhansip.xl.co.id
serial2024100300
refresh10800
retry3600
expire43200
minttl1800

How to solve problems with xl.co.id

Errors on the xl.co.id website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of xl.co.id on your own.