As per satyenshah's Jul 19, 2017 reply to this post:
The dedicated type=SPF record never really caught on. Sender policies using ``type=TXT records were established too well in the early 2000's for the type=SPF record to get a foothold in the 2010's. Your authoritative DNS server probably supports publishing the SPF record, but the Internet's MX servers ...
DNSviz do not see big problems, just warnings: https://dnsviz.net/d/dot.cf/XnjMRg/dnssec/
It may have been transient.
If you want to document it properly, your screenshot may not be enough. You should run dig commands towards each of the registry authoritative nameservers on .cf and record their reply for your domain.
In all cases like that, you have to ...
The reason for two or more name servers is for fault tolerance/redundancy. I've always seen at least two, one primary and a secondary name server, with possible replication to other name servers. I'm not sure, but the RFC may require a minimum of two as well.
That being said, I've never heard of the quantity of DNS servers impacting SEO. The numerous ...
The wildcard record you set up matches all subdomains. It does NOT match the domain apex. Your website doesn't work for the no-www domain because you do not have a DNS record for it.
To get it to work, you must create an A record for the domain apex (@) pointing to an IP address given to you by your hosting company. To do that, leave the type field ...
If you are using gsuite, your SPF record should be v=spf1 include:_spf.google.com ~all perhaps that will work since it is google generic SPF by the look of it.
That should mean that there are NS records for your subdomain at your main DNS host. Your DNS heirarchy should look like:
Domain registrar: NS records for example.com to main DNS host
Main DNS Host:
A record for example.com
A or CNAME record for www.example.com
NS records for api.example.com to route53
Route53: ALIAS records for api.example.com to the ...