This FAQ describes the most common problems that SafeScrypt encounters when authenticating requests for Server IDs.

1. You enrolled for the Server ID using an abbreviated name for the organization. For example, authentication fails if the organization's legal name is "Sue's Hair Design" but you enrolled using only "Sue's" as the name. Delays do not occur if you omit "Inc., Ltd." etc, from the Organization Name.

2. Authentication fails if the Proof of Right documents are not filed properly. For example, the organization's documents must have the State/Government Seal on them indicating that the documents have been received and filed with the State/Government. SafeScrypt cannot accept tax documents as valid business documents except in the case of non-profit organizations or sole proprietorships. (In either case, the tax documents must list the organization as non-profit or sole proprietor.)

3. All documents sent to SafeScrypt must be in English. Translated documents must be officially translated and this must be stated on them.

4. The Corporate Contact must directly work for the organization that requests the Server ID. In some cases an organization requests a Server ID through their ISP or Web Host. That is, the ISP/Web Host runs the server and possibly fills in the enrollment form. The ISP/Web Host is then the Technical Contact. However, the COrporate Contact must work for the company that is contracting with the ISP.

5. If the domain name is registered to another company, you must courier a signed letter stating this condition. Print and complete this document (download the letter here) on letterhead of the company that owns the domain name (Registrant) and have it signed by the Administrative Contact in the Domain Registry.
Note that you will need to resubmit this paperwork every year that you renew the Server ID. For this reason, it is much easier if the domain name is registered in the name of the organization that is requesting the Server ID.

6. If you submit a Banker Attested Letter in lieu of a phone number, the letter must be properly attested as per the guidelines in the enrollment guide.

7. The Common Name for the server that will use the Server ID must be a proper Common Name. That is, it is the host name plus the domain name. For example, digitalid.verisign.com is a proper Common Name. Submitting the host name digitalid or just the domain name verisign.com may make the enrollment invalid. SafeScrypt will need to contact you for the correct Common Name, which can delay your application.

If you believe your order contains one of these problems, E-mail or call SafeScrypt Customer Care so that your order can be updated with the correct information.

Support Information

Tel: 91-44-22540863
Fax: 91-44-22540771
E-mail: serverid_support@safescrypt.com