ERROR: Failed to fetch page due to: DnsResolutionRequestTimeout


I am validating my site for twitter card but it is not working.
my site is
please help me


It looks like our DNS cache cannot resolve your site’s address, so the crawler is unable to connect at the moment.


also experiencing this issue… is there any fix that can be put into place for this?

ERROR: Failed to fetch page due to: DnsResolutionRequestTimeout


Chiming in. Also having this problem.


We’ll need URLs to test against to understand what is going on here.



same problem


Hi we are getting the DNS error “ERROR: Failed to fetch page due to: DnsResolutionRequestTimeout” when using the testing tool .

Our domains are and we also used

Our ISP is not blocking twitters IP’s. Any help is appreciated.


We may have resolved this issue by updating the meta tag


Hi, I cannot get the card validator to work.
due to:
ERROR: Failed to fetch page due to: DnsResolutionRequestTimeout
Any Ideas?


How can i solve this?Is there any fix


I am also receiving this error on my site, is there any resolution?


which meta tags?


Having the same issue. It was working just fine up until a couple of days ago. No changes made on my site/server side.


This site looks fine now.


Unfortunately we’re not able to help with cards issues unless you can share a link. Make sure you’ve read the troubleshooting and FAQ post as well.


It was any link on my domain really ( It seems to be working again now though after a few days. Very odd.

Bryan Mendoza / Administrator / 818.277.8200

Note: In submitting material you are acknowledging you have legal rights to do so as owner or representative of said material and are thereby granting permission to use such material for broadcast on Sensimedia Radio stations.

Station ID’s and jingles are always welcome. While there is no script, they should include the basic information. Example: “This is (artist name) and you’re listening to Sensimedia Radio at”


Having the same issues here:

Any help is greatly appreciated!



Hi, I’ve got the same issue and no solution for now: and for all our articles.
Any help is appreciated.


Is there any chance that your host is blocking Twitter’s crawler IP addresses? Other than that, I’m not sure why there would be a DNS issue. Do you have any routing problems from any particular geographies?