add test for TXT record when vercel and remove invalid files

[gameroman]

Added a test for invalid TXT records and removed invalid ones

[is-a-dev-reviewbot]

Note

Please be aware that you put the pull request on draft mode when you created the pull request. If this isn't intentional, please scroll down until you find the "Ready for review" button and click it. We recommend not opening draft pull requests since we usually ignore it until it's no longer on draft mode.

Hi there! 👋

You've successfully made a pull request! Here are some steps to do while waiting for a maintainer to review the pull request:

1. Check if the checks have failed or passed. You should see the status at the bottom of the pull request or a icon next to the commit ID. You can click on the 3 dots next to the "CI / Tests" check then click "View details", it will show you the logs of the tests.
2. Check if the filename, file format, and records are valid. If you don't know if it's valid, please read this part of the documentation and use a JSON validator/formatter, like jsonlint. Make sure that the file is in the domains directory and not somewhere else in the repository.
3. Please make sure that you've filled out the pull request template. It is generally not a good idea to overwrite the pull request template with something else unless you know what you are doing. Make sure to add either a publicly available preview of your website or a screenshot of it.
4. Please wait patiently. Pull requests may take between a couple hours to 3 days. All of the maintainer team are volunteers and try to review the pull requests in their spare time.
5. Please note that mentioning maintainers in pull requests without it being reviewed could lead to you getting marked as "low priority"; this also applies to pinging the maintainers in the Discord server or messaging the maintainers in private to review the pull request.

Note

If you've opened this pull request while there is a high number of other open pull requests, your wait time will be longer than usual. Please be patient!

Note

We have recently launched another free subdomain service, is-a.bot!

Claim your .is-a.bot subdomain on GitHub.

[dragsbruh]

can you also remove any parent domains of these domains? only if they also are configured to use vercel ofc

make sure that the they didnt change it to a diff hosting provider later, in which case remove only the _vercel. file and leave parent untouched

would also be a good idea to check if the vercel record is in _vercel.domain.json and not domain.json or _vercel.sub.domain.json or stuff like that

would also recommend pinging owners of any domains you are removing

[gameroman]

can you also remove any parent domains of these domains? only if they also are configured to use vercel ofc

make sure that the they didnt change it to a diff hosting provider later, in which case remove only the _vercel. file and leave parent untouched

would also recommend pinging owners of any domains you are removing

I think that's out of scope for this PR currently

would also be a good idea to check if the vercel record is in _vercel.domain.json and not domain.json or _vercel.sub.domain.json or stuff like that

Yeah, I mentioned that in #48701 (comment)

I'd also do that in a separate PR probably

Lets see what @wdhdev thinks

oh well

[wdhdev]

Might be worth modifying the test so require them to be on _vercel nested subdomains & checking it somewhat matches the root subdomain, e.g. if it's on _vercel.william.is-a.dev the verification TXT(s) need to end with .william.is-a.dev or equal william.is-a.dev as nested subdomain Vercel verification records e.g. blog.william.is-a.dev go on _vercel.william.is-a.dev anyway (some people have arrays of TXT records).

Essentially just verify it's on _vercel and that the TXT matches the subdomain or a nested subdomain.

[gameroman]

Might be worth modifying the test so require them to be on _vercel nested subdomains & checking it somewhat matches the root subdomain, e.g. if it's on _vercel.william.is-a.dev the verification TXT(s) need to end with .william.is-a.dev or equal william.is-a.dev as nested subdomain Vercel verification records e.g. blog.william.is-a.dev go on _vercel.william.is-a.dev anyway (some people have arrays of TXT records).

Essentially just verify it's on _vercel and that the TXT matches the subdomain or a nested subdomain.

I can do it in this PR or in a follow-up PR