How to Verify Your Website on SEIPID?

After namespace approval, verify your registered website using a DNS TXT record, verification file, or HTML meta tag. Successful verification activates your namespace and its public page.

Protect your scholarly identity

Why is website verification important?

Your scholarly platform's name, content, and reputation can be misused by someone operating a copied or look-alike website. Such websites can mislead authors and readers into believing they are dealing with your organization. Website verification helps SEIPID connect your namespace to a website you or your organization control, supporting a more trustworthy public identity.

Help protect against impersonation

Copying a journal's name or website content does not demonstrate authority to represent it. SEIPID requires website verification alongside namespace review to help reduce unauthorized registrations and impersonation.

Give authors and readers confidence

A verified namespace connects your scholarly platform's identity, registered website, and public SEIPID page, helping authors and readers identify the website associated with your platform.

Keep that connection verified

SEIPID periodically checks your verification code. If it is repeatedly missing, we can contact you and review the namespace's verification status.

How it works

How do you complete verification?

  1. Find your codeAfter namespace approval, open Namespaces in the SEIPID Diwan portal to find your namespace verification code. It is also included in the approval email.
  2. Add the codeComplete any one of the three methods below. Use the code supplied for the namespace you are verifying.
  3. Run the checkIn the SEIPID Diwan portal, select Check now for that namespace. SEIPID also runs automatic verification checks periodically.
  4. Activate your namespaceSuccessful verification activates your namespace and its public page. You receive an email confirmation and can issue SEIPIDs within your account access and available balance.
Choose one method

Which verification method should you use?

Use DNS verification if you manage the domain's DNS records, a verification file if you can upload files, or a meta tag if you can edit the website's HTML header. Replace YOUR-CODE in the examples with the exact code supplied in the SEIPID Diwan portal.

Recommended

1. DNS TXT record

Recommended when you have access to the domain's DNS settings. The record is independent of your website software and can remain in place during a redesign.

DNS changes may not be visible immediately. If the check does not find a newly added record, allow time for the change to propagate and try again. Keep the verification record when changing DNS providers.
  1. Open the settings with the provider that manages your domain's DNS records. In cPanel, use Zone Editor. If you do not have DNS access, ask your domain administrator or choose another method.
  2. Add a new record of type TXT.
  3. For Name / Host, use the domain shown in the SEIPID Diwan portal. Your provider may accept @ for the root of its DNS zone or require the full domain name. A website hosted on a subdomain can also be verified using a TXT record on that subdomain.
  4. Value / Content:seipid-verification=YOUR-CODE
  5. Save the record, then select Check now in the SEIPID Diwan portal.
Requires file access

2. Verification file

Use this method if you can upload a text file to the website's document root, using a hosting file manager or FTP.

The file must be publicly accessible at the exact address shown in the SEIPID Diwan portal and return the verification code. If your hosting setup cannot serve it there, use DNS verification or an HTML meta tag.
  1. In Namespaces, select Download file for your namespace. The file name follows this format:seipid-verification-YOUR-CODE.txt
  2. Alternatively, create a plain text file with that exact name and only your verification code as its contents.
  3. Upload the file to the document root for the registered website's domain or subdomain. Use the location that serves the file address shown in the SEIPID Diwan portal.
  4. Open that address in a browser and confirm that it displays your code. For example:https://example.com/seipid-verification-YOUR-CODE.txt
  5. Select Check now in the SEIPID Diwan portal.
Requires HTML header access

3. HTML meta tag

Use this method if you can edit the website's HTML header. It can be suitable for a journal hosted on a shared OJS installation where DNS or document-root access is unavailable.

The tag must appear in the HTML <head> of the page at the exact website address registered with your namespace, as shown in the SEIPID Diwan portal.
  1. Copy the complete meta tag supplied in the SEIPID Diwan portal. It follows this format:<meta name="seipid-verification" content="YOUR-CODE">
  2. Add it to the page's HTML <head>. In OJS, your administrator can use the Custom Header plugin compatible with your installation. In WordPress or another content management system, use its supported method for adding header HTML.
  3. Save the change. If your website uses caching, refresh its cache so the updated HTML is publicly available.
  4. Select Check now in the SEIPID Diwan portal.
Good to know

Frequently Asked Questions (FAQs)

Why do I need to verify my platform’s website?

Website verification helps establish that you control the website associated with your scholarly platform. This helps reduce unauthorised registrations and impersonation through copied or look-alike websites. Verification works alongside namespace review to connect the registered platform, its website, and its public SEIPID record.

How can I verify my website?

After namespace approval, use the code supplied in the SEIPID Diwan portal to complete one of three methods: add a DNS TXT record, upload the verification text file, or add the HTML meta tag to the registered website. Choose the method that matches your access to the website, then select Check now in the SEIPID Diwan portal. Successful verification activates the namespace and its public page.

Should I keep the verification code after my website is verified?

Yes. Keep the verification DNS record, file, or meta tag in place. SEIPID checks it periodically. Repeatedly missing verification may lead to a request for action and a review of the namespace’s verification status. Remember to retain the code when redesigning the website or changing hosting or DNS providers.

What should I do if my platform moves to another domain?

Submit the new website through the namespace Metadata update process and explain the migration. Complete verification of the new address where requested. A website migration alone does not require a replacement NiD. Update the affected scholarly outputs’ source links separately so their existing SEIPIDs continue directing readers to the correct works.

What should I do if my website cannot be reached?

Check that the registered address is correct and publicly accessible. A firewall, bot protection, or a temporary hosting issue may prevent the verification check. DNS verification is an alternative because it checks DNS records rather than fetching a webpage.

Is there a deadline for verification?

Complete verification promptly after approval. Reminder emails are scheduled after 3, 7, and 14 days. Requests still awaiting verification after 30 days are flagged for review by the SEIPID team; the namespace remains inactive until verification succeeds.

Need help verifying your website?