Rated 1 out of 5 stars

by hurdingkatz on Sept. 1, 2014 · permalink

Not quite as out-of-the-box useable as described. For example *.con was corrected to *.con.cn. Don't know why (but I have a guess).

That's only one example of inexplicable "corrections" leading nowhere. Strangely, gmail.con became gmail.com. Go figure.

Even a search-and-replace entry was "corrected to a dotcn "domain," and it was correctly entered as dotcom.

If I'm going to be asked if a correction is correct, I'd like to say "yes," BEFORE the site is open. Given the unpredictable nature of the changes, I'd like to keep the door shut on some bad places, and I certainly don't want to go there unintentionally. It's quite different if I opt to use auto-correct. Then it's spin the wheel and take my chances.

The two stars are for the search-and-replace feature, since I can shorthand some regular addresses (even with the incorrect correction of my replacement entry). The jury's still out on the rest of it.

Update--One Day later: Now it's adding cpn to dotcom addresses, eg: place.cpn.com. Don't know why.

Telling it that the result is not correct does nothing. Next time out (using the same dotcom address), we just go 'round the same circle.

In one case, I've put an address on the do-not-correct list, yet it is constantly "corrected," to something wrong (dotcom changed to a domain I've never heard of nor can find when searched for.) Again, saying the correction is incorrect does nothing. It happens again and again.

Really unreliable. I fear I'll be sent to a "bad" address sooner or later if I keep using URL Fixer.

My guess to what's going on: The pool of collected "corrected" addresses is faulty and could be used to bend this useful idea to nefarious endeavors. Better to stick to correcting mistyped domains, and leaving customized corrections internal to the user's search-and-replace list.

Right now, based on my experience, URL Fixer can't be trusted.