Checking DNS pointing correctly to go daddy

Yes. And it has nothing to do with what I mentioned in my previous answer.

DNS records for designedaspirations.com look perfect.

DNS records for www.designedaspirations.com don’t

$ dig www.designedaspirations.com
www.designedaspirations.com. 3542 IN	CNAME	email.secureserver.net.
email.secureserver.net.	38	IN	A	45.40.130.41
email.secureserver.net.	38	IN	A	45.40.130.40
email.secureserver.net.	38	IN	A	45.40.140.6
email.secureserver.net.	38	IN	A	173.201.193.148

For some reason there is the CNAME record above which most certainly isn’t what you want.

Using +trace on dig also shows an additional CNAME record exists

$ dig CNAME www.designedaspirations.com +trace
# rest of output removed
www.designedaspirations.com. 3600 IN	CNAME	email.secureserver.net.
www.designedaspirations.com. 3600 IN	CNAME	autodiscover.outlook.com.
;; Received 127 bytes from 2a00:edc0:6259:7:1::4#53(dns4.p01.nsone.net) in 32 m

You need to remove these CNAME records from Netlify DNS and ensure the NETLIFY record for the www subdomain exists. If it doesn’t I’m sure @luke can help set it up again.