How to configure your Domain Linked Verifiable Credential

Knowledge Base

How to configure your Domain Linked Verifiable Credential

If you’re reading this, you’ve likely already downloaded your did-configuration.json file. Great! You’re just a few steps away from verifying your domain ownership using a Domain Linked Verifiable Credential (DLVC).

This guide will walk you through publishing the file on your website and verifying the setup.Great! Here’s a clean and professional draft for your wiki post titled “How to Configure Your Domain Linked Verifiable Credential” – written in clear English and step-by-step style.


Step 1: Download did-configuration.json

Make sure you’ve saved the file exactly as it was provided – do not modify its contents. This file is cryptographically signed and must remain intact.


Step 2: Publish the File at the Right Location

You need to make the file publicly accessible at:

https://yourdomain.com/.well-known/did-configuration.json

Note: The .well-known folder must be directly in the root of your domain.


Step 3: Platform-Specific Instructions

WordPress (Classic or Block Theme)

  1. Log in to your WordPress admin panel.
  2. Install the plugin: “File Manager” or use FTP / cPanel.
  3. Navigate to your root directory and create a folder called .well-known (if it doesn’t exist).
  4. Upload the did-configuration.json file inside .well-known.
  5. Visit: https://yourdomain.com/.well-known/did-configuration.json to make sure it loads.

⚠️ If you get a 403 Forbidden or 404 error, continue reading below (troubleshooting section).

WordPress + Elementor or page builders

Same as above – the file upload method does not change. Just ensure:

  • You’re working at the server or file manager level.
  • You’re not uploading this file as media content or trying to embed it in a page.

GitHub Pages

  1. In your repository, create a folder named .well-known in the root.
  2. Place your did-configuration.json inside.
  3. Commit and push.
  4. Verify the file at: https://yourdomain.github.io/.well-known/did-configuration.json

Netlify

  1. In your project folder, create public/.well-known/ and put the file there.
  2. Push your changes and redeploy the site.
  3. Test the file in your browser.

Vercel

  1. Same as Netlify – place the file inside /public/.well-known/.
  2. Deploy your changes.
  3. Test it live.

Common Issues & Troubleshooting

403 Forbidden (especially on Apache servers)

  • This happens when .well-known folders are restricted.
  • Fix: Edit your .htaccess file and add:
<Directory "/.well-known">
    Allow from all
</Directory>

Or simply:

RewriteRule ^\.well-known/ - [L]

404 Not Found

  • Double-check the file path and make sure your hosting provider doesn’t block dotfolders (.well-known).
  • Some CMS platforms like Wix or Shopify do not support custom folders like .well-known. In this case, you’ll need to host the file externally or use a subdomain that you control.

Final Step: Verify

Once the file is live at https://yourdomain.com/.well-known/did-configuration.json, the verification system will automatically detect it and validate your domain.

You’re done!


Need Help?

If you’re stuck or using a non-standard setup, feel free to reach out to our support.


Terms & Conditions Privacy - ObjectID is a service provided by SDV Consulting SRLS, VAT: IT 13168650961
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners. View more
Cookies settings
Accept
Privacy & Cookie policy
Privacy & Cookies policy
Cookie name Active

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Who we share your data with

If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where your data is sent

Visitor comments may be checked through an automated spam detection service.

Save settings
Cookies settings