dislike404.com Celebrates its First Anniversary!

A year ago, dislike404.com went live, and since then, quite a bit has happened.

News

There is now a news section to provide you with updates and background information about dislike404.com at (ir)regular intervals. When there's something new, you'll find it here 😎

Optimized User Area

You may have noticed, there have been several changes in the user area.

The results view has been completely revamped—the old design was merely functional. Results are no longer displayed all at once, as this caused issues when there were many errors.

Additionally, some improvements and new features have been added:

Detailed Scan Results

Details of every scan are now stored. All URLs checked by our crawler can now be viewed. Previously, you could only check the errors.

Search in Results

You can now search through the results of your scan.

View the Details During the Scan

You can now view the available results during the scanning process. Please note that the link hierarchy may not be complete at this time.

Optimization: Hits on a Blacklist

You will now see why our crawler did not check certain URLs. There can be various reasons for this:

• User Blacklist: URLs not checked because they are on your personal blacklist
• Global Blacklist: URLs not checked because we have excluded these URLs from being checked. This includes URLs that cannot be checked, such as 'tel:', 'mailto:' or script links.
• robots.txt: The URL was not checked because an entry in the site's robots.txt file does not want it to be checked.

Crawler Updates

Bugfixes

We have fixed some errors in the crawler; the scan results should now be even more accurate. The crawler can now handle redirects better and also stores them in the results list.

The crawler has been given a new technical foundation. The initial design proved impractical in many respects. Previously, the crawler had loose coupling via ActiveMQ, which has now been replaced with database coupling.

Website

• Some parts of the website have been revised
• Bugs have been fixed
• The Laravel framework has been updated to the latest patch level. Laravel 11 is still in use at the moment; an upgrade to Laravel 12 will follow later
• Unfortunately, it was necessary to implement a CAPTCHA for the registration and login areas. If you encounter issues please let me know.
• The deployment process has now been automated and optimized. There is no longer a short downtime during updates  🚀