Is who.is down or not working?

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

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

who.is outage reports in the last 24 hours

who.is - 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:
WHOIS Search, Domain Name, Website, and IP Tools - Who.is
Main page description:
Find information on any domain name or website. Large database of whois information, DNS, domain names, name servers, IPs, and tools for searching and monitoring domain names.
Protocol:
https
Status code:
200
Page size:
10.6 KB
Response time:
0.640sec.
IP:
18.204.185.62
Response headers:
date: Tue, 01 Oct 2024 01:57:21 GMT
content-type: text/html; charset=UTF-8
transfer-encoding: chunked
connection: close
set-cookie: AWSALBTG=InL15xucfAtfExtZBfPBgeHFekGuEwpbF0joFF0mXag0W9Y3I5LM0P0Ctufsam+2NaxDoY9juFNJkKnVn+9Q9HIDB6Hs2HNL3L7gwX8KBbmLPidi2klE3PvHHU7VfIkYObzZu1TBv8Mme/c8/Ru9IYH8NEQ4H6OVLyVdCsMjoFiO; Expires=Tue, 08 Oct 2024 01:57:21 GMT; Path=/,AWSALBTGCORS=InL15xucfAtfExtZBfPBgeHFekGuEwpbF0joFF0mXag0W9Y3I5LM0P0Ctufsam+2NaxDoY9juFNJkKnVn+9Q9HIDB6Hs2HNL3L7gwX8KBbmLPidi2klE3PvHHU7VfIkYObzZu1TBv8Mme/c8/Ru9IYH8NEQ4H6OVLyVdCsMjoFiO; Expires=Tue, 08 Oct 2024 01:57:21 GMT; Path=/; SameSite=None; Secure,AWSALB=lpYYhZYiONjcTUSxgs5Db065dUdfTY/jhNw0R/cyfM5sZNI5NV5UKrdReiM0tpmbRFU9osuvGZtQkkSsLjQmbLSXL81mjFlBayDrh+uXTU54F0Xc8lQny/+LoJzC; Expires=Tue, 08 Oct 2024 01:57:21 GMT; Path=/,AWSALBCORS=lpYYhZYiONjcTUSxgs5Db065dUdfTY/jhNw0R/cyfM5sZNI5NV5UKrdReiM0tpmbRFU9osuvGZtQkkSsLjQmbLSXL81mjFlBayDrh+uXTU54F0Xc8lQny/+LoJzC; Expires=Tue, 08 Oct 2024 01:57:21 GMT; Path=/; SameSite=None; Secure,WHOISSESSION=3tpfmuj6k4i3bhtjkq0ot5gg3b; path=/,Path=/; HttpOnly; Secure
server: nginx/1.24.0
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
DNS records:
A address18.204.185.62
ttl60
A address54.86.43.126
ttl60
NS valuens-232.awsdns-29.com
NS valuens-540.awsdns-03.net
NS valuens-1741.awsdns-25.co.uk
NS valuens-1048.awsdns-03.org
TXT entriesv=spf1 include:retailSPF.smtp.com ?all
TXT entriesgoogle-site-verification=oLW2qDgn-fqfI5FbmSTvDUXCLVKWL85jSwCJ3dRgSBM
SOA nsnamens-1048.awsdns-03.org
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

How to solve problems with who.is

Errors on the who.is 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 who.is on your own.