Is mxplayer.in down or not working?

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

What to do if the site mxplayer.in is not available? Try our guide.

mxplayer.in outage reports in the last 24 hours

mxplayer.in - 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

Main page title:
MX Player
Main page description:
MXPlay is a video streaming service and India's Maha entertainment destination.
Protocol:
https
Status code:
200
Page size:
2.0 KB
Response time:
0.779sec.
IP:
108.156.60.114
Response headers:
server: CloudFront
date: Tue, 01 Oct 2024 05:34:25 GMT
content-length: 2023
connection: close
content-type: text/html
x-cache: Error from cloudfront
via: 1.1 c00e79984dfec6a6601fb861a1d8d5e8.cloudfront.net (CloudFront)
x-amz-cf-pop: AMS1-P3
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: KEIJ3XlK4BQe_vJgccZHPrpOCKcn8YHetbgVKn2dt5mH4OL-Xx4l5Q==
x-xss-protection: 1
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
strict-transport-security: max-age=31536000; includeSubDomains; preload
DNS records:
A address108.156.60.33
ttl60
A address108.156.60.16
ttl60
A address108.156.60.73
ttl60
A address108.156.60.114
ttl60
MX exchangealt1.aspmx.l.google.com
priority5
MX exchangeaspmx.l.google.com
priority1
MX exchangealt2.aspmx.l.google.com
priority5
MX exchangeaspmx2.googlemail.com
priority10
MX exchangeaspmx3.googlemail.com
priority10
NS valuens-719.awsdns-25.net
NS valuens-2007.awsdns-58.co.uk
NS valuens-260.awsdns-32.com
NS valuens-1073.awsdns-06.org
TXT entriesDKIM Key : v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqT1uc5xkT19Bsk0RJmlm09iL61DEmMjAz9WpK7tALRFJvPp3aFpGovhYvaklgUVkTB3rROa94UHM3+0OfefWusAg040ra/FGPFP14iEK7JzyEqzuf/DMgpjcf94IY++FStwj3xj0skDRoAyOvsOQ8yrfBYlEYzte7Cs0i0F3Fw+
TXT entriesgoogle-site-verification=8k8JbowLD74CdWxlAoOCQ8HBPhEKiiVWlQ06bJaaTC4
TXT entriesgoogle-site-verification=EorM2CwayrafMMSsqbarOa9IRC3WzrKi3TLxLnBNyD0
TXT entriesDKIM Key : v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCeWwvARkGs0Czx3Gj690INc8jkrkqSAh/Kp8sp/+0WcYCe1un8Tl0HIbyF4rPC0jvydJKH95XwNL1ZLQsEvgZFcuMpug0pSMeIynrDLUrqeRNjJpS0IgabGOLVFBG+4w6sVQjDrGzJ3/JOmAd7awYtlVc5jA0aya1a1bQSTNyYuQIDAQAB
TXT entries2QRREIX2IbGtSJB2v2oV6QKOUGQYxx4SfYkvkRTYema9rzpNq7kfODk5SOSVGbCjpkoOO7EurKsoXBz779h1MMLBaNkmLYsx1nCkyYQJDUSCNN8sWNlMmSKP7pGzRvUzjbMgiBWhN+sd7DU7Wq5nC0yxAuaOqTUU8kJD0fQWmPQIDAQAB
TXT entriesgoogle-site-verification=DEmpW_U-Urvv8M5duD714g1OOKS03HNgminLNpzpuE0
TXT entriesv=spf1 include:_spf.google.com -all
SOA nsnamens-719.awsdns-25.net
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

SEO headers

h1 Oops!!!
h2 We are currently not available in your region.

How to solve problems with mxplayer.in

Errors on the mxplayer.in 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 mxplayer.in on your own.