Is wbsedcl.in down or not working?

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

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

wbsedcl.in outage reports in the last 24 hours

wbsedcl.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:
Welcome to WBSEDCL
Protocol:
https
Status code:
200
Page size:
44.2 KB
Response time:
4.503sec.
IP:
122.15.179.8
Response headers:
content-length: 45306
date: Wed, 02 Oct 2024 05:43:57 GMT
cache-control: private
accept-ranges: bytes
etag: "8126078132627"
last-modified: Mon, 30 Sep 2024 07:06:13 GMT
content-type: text/html
set-cookie: saplb_*=(J2EE6125220)6125250; Version=1; Path=/; Secure; HttpOnly,JSESSIONID=FWXzg5Pjog1o9agO9Tv5iyo5r8FLkgHCdl0A_SAPlur_2gesDjD9Z13usT-sRD3a; Version=1; Path=/; Secure; HttpOnly
connection: close
strict-transport-security: max-age=31536000
x-frame-options: SAMEORIGIN
referrer-policy: strict-origin-when-cross-origin
x-content-type-options: nosniff
access-control-allow-origin: https://epension.wbsedcl.in
access-control-allow-headers: application/json,Authorization,Content-Type
access-control-allow-credentials: true
DNS records:
A address1.7.209.202
ttl600
A address122.15.179.8
ttl600
MX exchangesmtpavpr.wbsedcl.in
priority10
NS valuens3.wbsedcl.in
NS valuens1.wbsedcl.in
NS valuens2.wbsedcl.in
NS valuens4.wbsedcl.in
TXT entriesqt7vqs8w1xy1q7fx307prfnk7kl5zd3j
TXT entries_globalsign-domain-verification=1b618XR1u3lbMfJo-8QSBEI8mGJpwTcyTS5n-qgqGA
TXT entriesgoogle-site-verification=0n3TLhv-Jk6UkjLVNe6LG_7mXNMktnpgK-g1KbMqNzQ
TXT entries_globalsign-domain-verification=M2V0kI5rww6nAt9PIo3_tlIoLyeSjt_STD4fjwjHsF
TXT entriesv=spf1 a:smtpavpr.wbsedcl.in mx ip4:1.7.209.205 ip4:122.15.179.10 include:spf.protection.outlook.com ~all
TXT entries_globalsign-domain-verification=WzYp0mHyyddslcuXTjG_kMeBs-g-VQfVfibG-DTsDc
TXT entries_globalsign-domain-verification=dYV3YWC5Ugzx8yVrzn1B5uLaHyg10aEaSzjjrwuGgs
TXT entriesMS=6CF5390122954EBDBADD6CEDD5166C48AD0E1A33
SOA nsnamens1.wbsedcl.in
hostmasternsmail.wbsedcl.in
serial2022040601
refresh10800
retry900
expire1209600
minttl86400

How to solve problems with wbsedcl.in

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