domain.example is encouraged for documentation, but you can also use something like example.invalid.
Whenever I review unit tests that have URLs in them, I insist that they use the .invalid TLD. I know that .test is encouraged, but I find that .invalid stands out more when you're browsing a test suite.
The old argument against this was that the average person is really only familiar with .com, .org, and maybe .net, and they wouldn't even recognize something with a less commonly used TLD as a domain name.
But with the rise in popularity of alternate TLDs, I don't think that argument is as persuasive anymore.
example.com. 8367 IN A 184.108.40.206
So if you want to demonstrate what a working domain looks like you need something else.
laughed and promised myself that i will never submit another bug to Google ;)
Small nitpick: this is spottedfig dot com, a domain which they still control.
https://www.icann.org/resources/pages/gtld-lifecycle-2012-02... has a graphic explaining a typical domain lifecycle.