Archives

Namecheap coupons for Domain Name services – April 2018

There are no affiliates links or affiliates coupon codes on this page!

We don’t offer domain name services anymore, and many users ask us what company to use. We recommend Namecheap for domain name services. Here we will list the monthly Namecheap coupons.

Valid Period: April 1 – April 30, 2018
Coupon Code: WEBBLOSSOM

The coupon code entitles you to register or transfer your .com, .net, .org, .biz, .info at the following discounted rates:
COM Registration $9.95 + $0.18 ICANN Fee
COM Transfer $8.84 + $0.18 ICANN Fee
NET Registration $12.09 + $0.18 ICANN Fee
NET Transfer $11.19 + $0.18 ICANN Fee
ORG Registration $11.51 + $0.18 ICANN Fee
ORG Transfer $10.21 + $0.18 ICANN Fee
INFO Registration $11.23 + $0.18 ICANN Fee
INFO Transfer $11.23 + $0.18 ICANN Fee
BIZ Registration $12.08 + $0.18 ICANN Fee
BIZ Transfer $12.08 + $0.18 ICANN Fee

You can find all the Namecheap coupons for the current month at https://www.namecheap.com/promos/coupons.aspx

Share this post:

How to force HTTPS via .htaccess

Nowadays most web browsers will show a warning when you visit a site that is not using an SSL certificate. The message looks like in Chrome Web Browser:

chrome insecure site

Your connection to the site is not secure.
You should not enter any sensitive information on this site (for example, passwords or credit cards), because it could be stolen by attackers.

To fix this message you should install an SSL certificate. You can buy one, or if you are using cPanel, you can ask your host to install one for free for you. cPanel offers free SSL certificates (powered by Comodo).

When loading the same site – which now have an SSL certificate installed – you will see:

chrome secure site

Secure connection.
Your information (for example, passwords or credit card numbers) is private when it is sent to this site.

Now you probably will want to redirect requests made to http to https. Do do this, edit the .htaccess file in your site’s and add the following lines to the beginning of it (replace domain.com with your domain name):

RewriteEngine On
RewriteCond %{SERVER_PORT} 80 
RewriteRule ^(.*)$ https://www.domain.com/$1 [R=301,L]

If you don’t want to use www in URLs, use:

RewriteEngine On
RewriteCond %{SERVER_PORT} 80 
RewriteRule ^(.*)$ https://domain.com/$1 [R=301,L]

Related KB article: How to force www or non-www URLs for your domain via .htaccess in cPanel

Share this post:

What’s the example.com domain?

Have you ever asked what the example.com domain represents? We will give you some details here.

Example.com (example.org, example.net) are domains that can be used as examples in documents/papers/websites etc. They were specifically created by IANA to be used as example domains.

IANA is an acronym for Internet Assigned Numbers Authority. For more information check their website.

So, if you navigate in your browser to http://www.example.com  you will see a webpage with a simple message:

Example Domain

This domain is established to be used for illustrative examples in documents. You may use this domain in examples without prior coordination or asking for permission.

example.com domain

Clicking on the More information link you are redirected to IANA’s webpage at https://www.iana.org/domains/reserved. Here we find the purpose of the example domains:

As described in RFC 2606 and RFC 6761, a number of domains such as example.com and example.org are maintained for documentation purposes. These domains may be used as illustrative examples in documents without prior coordination with us. They are not available for registration or transfer.

In RFC 6761 at clause 6.5 we find considerations for the example reserved domains:

6.5. Domain Name Reservation Considerations for Example Domains

The domains “example.”, “example.com.”, “example.net.”,
“example.org.”, and any names falling within those domains, are
special in the following ways:

1. Users SHOULD understand that example names are reserved for use
in documentation.

2. Application software SHOULD NOT recognize example names as
special and SHOULD use example names as they would other domain
names.

3. Name resolution APIs and libraries SHOULD NOT recognize example
names as special and SHOULD NOT treat them differently. Name
resolution APIs SHOULD send queries for example names to their
configured caching DNS server(s).

4. Caching DNS servers SHOULD NOT recognize example names as special
and SHOULD resolve them normally.

5. Authoritative DNS servers SHOULD NOT recognize example names as
special.

6. DNS server operators SHOULD be aware that example names are
reserved for use in documentation.

7. DNS Registries/Registrars MUST NOT grant requests to register
example names in the normal way to any person or entity. All
example names are registered in perpetuity to IANA:

 

Domain Name: EXAMPLE.COM
Registrar: RESERVED-INTERNET ASSIGNED NUMBERS AUTHORITY
Whois Server: whois.iana.org
Referral URL: http://res-dom.iana.org
Name Server: A.IANA-SERVERS.NET
Name Server: B.IANA-SERVERS.NET
Status: clientDeleteProhibited
Status: clientTransferProhibited
Status: clientUpdateProhibited
Updated Date: 26-mar-2004
Creation Date: 14-aug-1995
Expiration Date: 13-aug-2011

IANA currently maintains a web server providing a web page explaining
the purpose of example domains.

Share this post:
Page 2 of 2
1 2