aaa.josh.rs Open in urlscan Pro
185.254.198.220  Public Scan

Form analysis
0 forms found in the DOM

Text Content

MUTT'S DOWNTIME RESOLVER


AUTODIAGNOSTIC CHECKLIST

Your are online.

Querying kiwifarms.hk NS records.

Connection is IPv4 capable.

Connection is IPv6 capable.

Received NS records.

ult01.dnspod.com., ult02.dnspod.com.

NS records are consistent.

Querying kiwifarms.hk AAAA records.

Querying kiwifarms.hk A records.

Received A records.

45.144.29.67, 86.107.179.19, 86.107.179.20, 86.107.179.21, 86.107.179.22,
89.221.224.80, 89.221.225.73, 94.131.3.118

Received AAAA records.

2a09:7c41:0:39::1

AAAA records are consistent.

A records are consistent.

45.144.29.67 responded.

86.107.179.19 responded.

86.107.179.20 responded.

86.107.179.21 responded.

86.107.179.22 responded.

89.221.224.80 responded.

89.221.225.73 responded.

94.131.3.118 responded.

[2a09:7c41:0:39::1] responded.

All healthchecks passed.

This indicates the service is up and reachable from your Internet connection.


DIAGNOSIS: OFFLINE

Your browser reports you are offline. Check your Internet connection.


DIAGNOSIS: PROBLEMATIC FIREWALL

Public DNS providers were not able to be contacted for DNS-over-HTTPS (DoH)
lookups. This is very unusual, especially since your browser believes it is
connected to the Internet.


CAUSE 1: YOU'RE ACTUALLY OFFLINE.

Your browser thinks you are online, but this is not always correct. Please check
your Internet connection.


CAUSE 2: PUBLIC WIFI

If you are connected to public wifi, you usually have to accept terms of
service.

Because these ToS pages are technically man-in-the-middle attacks, you have to
open an http:// page to get a redirect. Try this link.




DIAGNOSIS: AUTHORITATIVE NS REPLY

Public DNS has replied to the query with the root authority. This indicates the
domain is not in valid standing. Either it is unregistered, expired, or has been
put on hold by the root authority. Check social media for updates.

Network Information Centers (NICs) control all domains ending with the .tld they
are responsible for. For example, VeriSign controls .com, .net, and many others.
These are private companies accredited by ICANN. They each maintain their own
rules. Most TLDs associated with a country are controlled by government or
academic entities.


DIAGNOSIS: MISMATCHED NS RECORDS

Different public DNS providers have replied to our NS query with different NS
records. This is unusual, especially if the NS records are from totally
different providers.


CAUSE 1: ROOT NS UPDATE

The domain owner has updated the NS and the changes are still propagating.


CAUSE 2: DOMAIN PARKING

The domain was parked by a hostile domain registrar and the seizure is still
propagating.


DIAGNOSIS: SERVERS UNREACHABLE.

No severs responded to healthchecks.


CAUSE 1: SERVERS ARE DOWN.

The servers may be down or service may be disconnected. You should check social
media for updates.


CAUSE 2: DELIBERATE NETWORK OBSTRUCTION.

Servers can be made unreachable by nullrouting or other network manipulation.
Tech savvy users can further diagnose this issue by using traceroutes to see if
the trace ends at one of the usual suspects (notably, Cogent).


DIAGNOSIS: PARTIAL SERVICE DEGREDATION.

Only some servers properly responded to healthchecks. You may be able to connect
intermittently until the issue is resolved. This is because the server you
connect to is picked at random, and your browser may select the wrong one
sometimes.


CAUSE 1: SERVERS ARE DOWN.

The servers may be down or service may be disconnected. You should check social
media for updates.


CAUSE 2: DELIBERATE NETWORK OBSTRUCTION.

Servers can be made unreachable by nullrouting or other network manipulation.
Tech savvy users can further diagnose this issue by using traceroutes to see if
the trace ends at one of the usual suspects (notably, Cogent).


DIAGNOSIS: IPV4 NATIVE

The Kiwi Farms is currently running with only A records, which supplies IPv4
addresses. However, your network does not appear to support IPv4. This means you
will not be able to connect.

It is very unusual for a network to not support IPv4 connections at all. Your
network may be misconfigured, or you may have a firewall that is only blocking
IPv4 traffic.

You can connect to an IPv4 service without your ISP providing IPv4 support by
using a VPN that provides 4in6 tunnelling (such as Mullvad), or by using
Tor-over-Clearnet. Just connect to Tor and put in the regular URL.


DIAGNOSIS: IPV6 NATIVE

The Kiwi Farms is currently running with only AAAA records, which supplies IPv6
addresses. However, your network does not appear to support IPv6. This means you
will not be able to connect.

The service may be in IPv6 native mode as a form of DDoS hardening. Most
computers compromised as part of a botnet are old and run IPv4 only. IPv6
nativity helps the service stay up.

You can connect to an IPv6 service without your ISP providing IPv6 support by
using a VPN that provides IPv6 (such as Mullvad), or by using Tor-over-Clearnet.
Just connect to Tor and put in the regular URL.


DIAGNOSIS: NO ISSUES FOUND

This indicates you have an Internet connection which can reach the Kiwi Farms.
You should be able to load the site. If you cannot, there are other
explanations.


CAUSE 1: DNS HIJACKING

This tool uses public DNS and DNS-over-HTTPS. It does not use the DNS you are
actually using to resolve the domain. It is not possible for this tool to
diagnose if your actual DNS provider is resolving the domain correctly. If you
have never manually changed your DNS, you are using your ISP's default DNS and
they may be blocking the domain.

On Windows, open a command prompt and type:
nslookup website.com

On Mac or Linux, open a terminal and type:
dig website.com

If the output does not match the records seen on your diagnostic checklist, your
DNS provider is likely blocking the domain. Please report this issue and tell me
which ISP you were using.

If you do not understand these instructions but want to change your DNS anyways,
visit Quad9, Cloudflare DNS, or Google DNS. Alternatively, most VPNs will use
their own DNS and Tor-over-Clearnet should always work.