Blog

As I pointed out in my previous article, “where the heck is my domain name?“, nothing ruins one’s morning worse than waking up and finding your (former) domain name for your church now redirects unsuspecting visitors to a grotesque gaggle of naked Russian women.

And just to drive the point home, I’ve collected a series of articles that I hope will scare the boogers out of you enough to go check the ownership and status of your church’s domain name(s) — and then tatoo the expiration date to your forehead and arm.

• Defend your domain from Web porn – If you don’t know when your church’s or organization’s Web domain expires, you might want to check — before pornographers do.
• Adult Site Operators Increase Hijacking Of Expired Domain Names – Over the last several months, domain name speculators have begun to register lapsed domain names that were previously owned by commercial entities, non-profit organizations, religious groups and local governments. In many cases, the speculators link their new names to adult content.
• Google and dmoz lose expired domains fight – I often see domains which are in different dmoz and google categories (children, news, disabled people, church, government ..) with porn content … Seems to me like people register expired domains which are still
  in dmoz and get high PR for their sites from both, Google and dmoz categories.
• Christian Web sites being ‘hijacked’ by pornographers – Christian ministries are inadvertently becoming purveyors of smut as pornographers “hijack” expired Web sites, either to lure unsuspecting visitors to pornographic sites or to earn a profit by selling the URL back to its original owner at an inflated price … The Indiana Baptist newspaper is among the latest victims of a scheme that has affected various ministries, non-profit organizations, government agencies and political leaders.
• Sites Forlorn When Reborn as Porn – Small town governments, church groups and the Ohio State Senate have Web addresses that have been hijacked and held ransom by pornographers lately in a growing trend. By Jeffrey Benner.

One of my more frequent reads, the Register, is running a very informative series of article entitled “Where the hell is my website?.” The third installment in this series, “A punter’s guide to keeping hold of your domain” offers several points you should print out and keep by your computer. Or at least keep in the notebook or folder you use to manage your site. You do keep such records and notes don’t you?! More on that later.

The bottom line is that some of you lose your church web sites because you lose control or ownership of your domain name. So, here for your convenience, are just the bullet points without the excellent explanations offered in the aforementioned article with some emphasis on one particular point I find VERY important.

Meaning, when you get a chance, read the article. In fact, read the entire series or you too might find yourself dying a thousand painful deaths when you wake up one morning, type in your church’s domain name, only to find yourself redirected to a pr0n site:

• Do NOT let your domain expire
• Make sure you are listed as the Administrative and Technical contact
• Make sure those contacts are correct
• Do NOT let your domain expire
• Go to a reputable registrar
• Try to choose a registrar with an online control panel
• Check the registrar charges
• Do NOT let your domain expire
• Get a registrar that locks a domain
• Check the registrar’s security
• Do NOT let your domain expire
• And if it has already expired?

Here is an interesting article by way of UC Berkeley’s Computing and Communications newsletter. It offers an exhaustive description of the various methods one can employ to fend off evil spammers (yes, I know those last two words are redundant).

Here are some bullet points of the various tactics you can employ on your church web site:

• return your address through JavaScript
• accepting email via contact forms
• obscuring addresses
• requiring authentication to view private pages
• redirecting harvesting tools

Now go read the article and read the pros and cons of each of the above methods.

Mark Pilgrim reverses a previous position on CSS hackery by handling browser differences with mod_rewrite. The end effect is that each page links to two stylesheets: mu.css and om.css. Everybody gets mu.css, and the bulk of his styles are defined there. But for browser-specific workarounds, om.css gets redirected based on rules Mark set up in his .htaccess file.

An interesting approach I’ll be keeping my eye on. Meanwhile, here’s some more goodies on mod_rewrite we’ve previously discussed here at HealYourChurchWebSite:

• Link Rot vs. mod_rewrite – round 1
• Son of Not So Simple Redirect
• Not so Simple Redirect (non mod_rewrite)