Is jd.id down or not working?

What happened to jd.id, why did the website go down and not work? Here you can see who else is having the same problem with jd.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, jd.id is working fine, but single failures are possible. If jd.id does not work for you, then report your problem and write a comment.

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

jd.id outage reports in the last 24 hours

jd.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

DNS records:
MX exchangemx1.jd.com
priority10
NS valuens1.jd.id
NS valuens2.jd.id
TXT entriesgoogle-site-verification=or0uz03OYu9xy0UPWnCUxbfG_vxUkSdBvkjs7bbd0K8
TXT entriesMS=45F82CF8ED6571D4D07E4C46D5442779E42763EA
TXT entriesahrefs-site-verification_f9dc681efebba6b936307c74ae3966b534efb07c04b871c0e676683875d6714a
TXT entriesv=spf1 include:c.spf.jd.id include:d.spf.jd.id -all
TXT entriesfacebook-domain-verification=ixs4zgdvz1tog59ajqurz291lhaieq
TXT entriesgoogle-gws-recovery-domain-verification=36599659
SOA nsnamens1.jd.com
hostmasterapollo.jd.com
serial2015108427
refresh10800
retry3600
expire604800
minttl38400

How to solve problems with jd.id

Errors on the jd.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 jd.id on your own.