Is dbcls.jp down or not working?

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

What to do if the site dbcls.jp is not available? Try our guide.

dbcls.jp outage reports in the last 24 hours

dbcls.jp - 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:
DBCLS ｜ ライフサイエンス統合データベースセンター
Protocol:
https
Status code:
200
Page size:
17.5 KB
Response time:
2.379sec.
IP:
52.52.188.181
Response headers:
date: Tue, 01 Oct 2024 16:05:04 GMT
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Tue, 01 Oct 2024 08:36:11 GMT
access-control-allow-origin: *
etag: "66fbb47b-4be8"
expires: Tue, 01 Oct 2024 08:49:23 GMT
cache-control: max-age=600
x-proxy-cache: MISS
x-github-request-id: F9AB:3C22F2:106B0E5:10DFA14:66FBB53A
accept-ranges: bytes
age: 0
via: 1.1 varnish
x-served-by: cache-sjc10045-SJC
x-cache: HIT
x-cache-hits: 0
x-timer: S1727798704.008831,VS0,VE79
vary: Accept-Encoding
x-fastly-request-id: bace33dcfb13fb06582f97fc66143fda5797b44a
connection: close
transfer-encoding: chunked
DNS records:
A address52.52.188.181
ttl3600
MX exchangeaspmx2.googlemail.com
priority10
MX exchangemailsender.ddbj.nig.ac.jp
priority20
MX exchangealt1.aspmx.l.google.com
priority5
MX exchangeaspmx3.googlemail.com
priority10
MX exchangeaspmx.l.google.com
priority1
MX exchangealt2.aspmx.l.google.com
priority5
NS valuens-100.awsdns-12.com
NS valuens-1911.awsdns-46.co.uk
NS valuens-791.awsdns-34.net
NS valuens-1065.awsdns-05.org
TXT entriesglobalsign-domain-verification=TbRqCj3G13fPEBD_rKW0tm4zRU67qEV7NsHqg1240-
TXT entriesv=spf1 include:_spf.google.com ~all
TXT entriesgoogle-site-verification=POX3YzwSYJLsJofLw5f6AXA0bE8j0YoSlHpJVJ3S9Kk
TXT entrieswYKgJZ0hyi2o12/jMIrkUxgm58Q4hUbknbLzSS9ryvU=
SOA nsnamens-100.awsdns-12.com
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

SEO headers

h2 TogoDX/human
h2 TogoID
h2 BioHackathon
h2 統合TV
h2 関連機関との連携
h2 DBCLSの研究開発
h2 News
h2 Site map
h2 Address
h2 Links

How to solve problems with dbcls.jp

Errors on the dbcls.jp 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 dbcls.jp on your own.