# Add a domain to get started - validate domain - failed **URL:** \ **Category:** Elastic Search\ **Created:** [October 31, 2021, 7:34am UTC](https://discuss.elastic.co/t/add-a-domain-to-get-started-validate-domain-failed/288077 "2021-10-31T07:34:37Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![neergttocsdivad](https://avatars.discourse-cdn.com/v4/letter/n/43a26b/32.png) [@neergttocsdivad](https://discuss.elastic.co/u/neergttocsdivad)\ **Post date:** [October 31, 2021, 7:34am UTC](https://discuss.elastic.co/t/add-a-domain-to-get-started-validate-domain-failed/288077/1 "2021-10-31T07:34:37Z")
A first try, using python3 http.server Suggestion gratefully received ![Screenshot from 2021-10-31 07-23-39](https://us1.discourse-cdn.com/elastic/original/3X/3/4/34d02e3b19655b3202755ab3c0db3f04184775e1.png) ---
**Author:** ![ross.bell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross.bell/32/77559_2.png) [@ross.bell](https://discuss.elastic.co/u/ross.bell)\ **Post date:** [November 1, 2021, 4:28pm UTC](https://discuss.elastic.co/t/add-a-domain-to-get-started-validate-domain-failed/288077/2 "2021-11-01T16:28:40Z")
Hey @neergttocsdivad, What version of Enterprise Search are you running? By default, crawls against `127.0.0.1` wont work for security reasons. If you need to override this for testing, you can do so with a configuration option. Look for `Crawler HTTP Security Controls` and `Crawler DNS Security Controls` here: [Configuration | Elastic Enterprise Search Documentation [7.15] | Elastic](https://www.elastic.co/guide/en/enterprise-search/7.15/configuration.html). I hope that helps! Ross ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 8:32am UTC](https://discuss.elastic.co/t/add-a-domain-to-get-started-validate-domain-failed/288077/3 "2022-11-04T08:32:52Z")