[Skullmeat]

So recently, firefox has been asking me "Did you mean to go to x.domain?" anytime I typed anything in my URL bar. It's only supposed to do that when it tries to resolve a domain after the search. I found this to be odd, as going to any of the suggested urls brought up a 404 page, but not the standard "not found" firefox normally does. This was driving me crazy, so I decided to dig deeper. I did find some information saying the ISPs may have their own redirect pages, but this was not like that, and I use googles DNS or cloudflare's DNS servers. My next course of action was to check for a DNS leak, it was clean. Trying to isolate the problem, I decided to run a traceroute, not expecting anything to come up. However, I noticed something odd. Bogus domains were resolving to a hosting service by Majestic hosting. Fearing the worst, I began a scan of my system. Further research showed the host was in texas. The scan turned up nothing, and out of desperation, I took a second look at my traceroute, and something else caught my eye: the bogus url I had put in to trace was actually resolving to a subdomain, xxxx.skullmeat.com. I thought "what the fuck? why is that happening?" Then it hit me: skullmeat.com was the throwaway domain I had set for my cisco router (its used for SSH, etc). Acting on a hunch, I changed the routers domain, and the problem went away. So not only did someone have the skullmeat.com domain, it was a host in texas! What are the odds?

TL;DR: Someone had the same domain my router used which caused every random url I typed in to resolve to a subdomain.

[mothered]

So not only did someone have the skullmeat.com domain, it was a host in texas! What are the odds?

Next to nothing.

In my 30+ years of computing, I don't recall experiencing anything of the sort.
You did very well with your troubleshooting and Isolation tests.

[Skullmeat]

So not only did someone have the skullmeat.com domain, it was a host in texas! What are the odds?

Next to nothing.

In my 30+ years of computing, I don't recall experiencing anything of the sort.
You did very well with your troubleshooting and Isolation tests.

I'm looking into why this happens, and what I can do to prevent it in the future.

[mothered]

So not only did someone have the skullmeat.com domain, it was a host in texas! What are the odds?

Next to nothing.

In my 30+ years of computing, I don't recall experiencing anything of the sort.
You did very well with your troubleshooting and Isolation tests.

I'm looking into why this happens, and what I can do to prevent it in the future.

It's got me at a loss, I've never seen anything like It.

I'll also do my own research but If you happen to find the cause, please quote me.