Is Doi Down?

I have a problem with doi.org

Are you having issues? Provide feedback to Doi by selecting the option you are having issues with.

Something else...

Site Online

User reports:
No current problems

User reports 0

doi.org problems reported in the last 24 hours

24 hour clock

Most reported problems

Doi.org Server Status

Response Header
HTTP headers carry information about the client browser, the requested page and the server status

HTTP/2 200 
content-type: text/html
content-length: 7449
last-modified: Thu, 13 May 2021 21:36:40 GMT
server: AmazonS3
date: Thu, 10 Feb 2022 07:06:39 GMT
etag: "1b1173de3494fb951ac3096fb445c95b"
vary: Accept-Encoding
x-cache: Hit from cloudfront
via: 1.1 ba93d64cb248ed4a264c9ee401175456.cloudfront.net (CloudFront)
x-amz-cf-pop: EWR52-C4
x-amz-cf-id: TzP7Unf-7RxXtZrAZH7zOoNeyG8h5-c1LQU6X9Qydw4ipvyoAxQ1rg==
age: 1758

DNS Records
DNS Resource Records associated with a hostname

The DNS is up. We have tried pinging Doi.org. There are no DNS Issues detected!

Type	Name	Value	Class	TTL
A	doi.org	104.26.8.237	IN	300
A	doi.org	104.26.9.237	IN	300
A	doi.org	172.67.72.147	IN	300
NS	doi.org		IN	86400
NS	doi.org		IN	86400

Safety

HTTPS Encryption

HTTPS Encrypted.

Is Doi safe?

Yes Doi.org is Safe according to Google Safe Browsing

Speed

Response Time

The website responded in 0.24 seconds.

Pagesize

The size of the HTML webpage is 2.86 kB.

Text compression

Webpage is Compressed: The filesize is 2.86 kB.

How to Solve Doi.org Down or Outage Issues

We have tried pinging Doi.org using our servers and the Doi.org server responded on time, indicating that there are no current Doi.org problems today.

If Doi.org is down for you too, the server might be overloaded or unreachable because of network problems, outages or a website maintenance is in progress.

If Doi.org is UP for us but you cannot access it, try these solutions:

Do a full Browser refresh of the site holding down CTRL + F5 keys at the same time on your browser
Clear Your browser Cookies and Cache
Fix DNS problems by Clearing your local DNS cache to make sure that you grab the most recent cache that your ISP has