Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
Whether this affects everyone or only your network decides what comes next, and a quick check will tell you. Enter attirand.rf.gd on dnschecker.org with record type A. Then, if you can, run these two commands and post the output:
nslookup attirand.rf.gd
nslookup attirand.rf.gd 1.1.1.1
Please also tell me your internet provider and country.
The knowledge base article on this error explains why. If most locations on dnschecker.org fail, the problem is with the domain itself. If most work, your network’s DNS server is returning “not found”. The article says some networks do this for free subdomains, and that it’s invisible from our side, so user reports are how those blocks get found.
Your account with that subdomain is active and was created well over 72 hours ago. The article says a free subdomain listed in your account needs no setup, so waiting isn’t the answer here.
The incident currently open on the status page is about a different domain, howto.rocks, so it doesn’t describe what you’re seeing.
Others have reported the same error on rf.gd subdomains recently, for example this topic. I can’t tell yet whether yours is the same problem, and the check above would show whether it is.