DNS audit for metaviewerap.com created on 2026-04-22 19:24:21

1. Name servers

Name servers listed at the parent server d.gtld-servers.net:

mfns1.metafile.com
mfns2.metafile.com
mfns4.metafile.com

Result: 3 name servers found at the parent server (set at the domain provider).
Recommendation: Everything is okay. There is more than one name server added to metaviewerap.com.

2. NS records

NS records returned by each name server configured for the domain name

Frankfurt, DE San Francisco, US Sydney, AU Singapore

mfns1.metafile.com [109.201.133.196] (8ms):
mfns1.metafile.com
mfns2.metafile.com
mfns3.metafile.com
mfns4.metafile.com

mfns2.metafile.com [108.62.121.219] (84ms):
mfns1.metafile.com
mfns2.metafile.com
mfns3.metafile.com
mfns4.metafile.com

mfns4.metafile.com [20.95.55.2] (121ms):
108.62.121.219
109.201.133.196
185.136.97.79
20.95.55.2
MFNS1.metafile.com
MFNS2.metafile.com
MFNS3.metafile.com
MFNS4.metafile.com

mfns1.metafile.com [109.201.133.196] (138ms):
mfns1.metafile.com
mfns2.metafile.com
mfns3.metafile.com
mfns4.metafile.com

mfns2.metafile.com [108.62.121.219] (70ms):
mfns1.metafile.com
mfns2.metafile.com
mfns3.metafile.com
mfns4.metafile.com

mfns4.metafile.com [20.95.55.2] (40ms):
108.62.121.219
109.201.133.196
185.136.97.79
20.95.55.2
MFNS1.metafile.com
MFNS2.metafile.com
MFNS3.metafile.com
MFNS4.metafile.com

mfns1.metafile.com [109.201.133.196] (276ms):
mfns1.metafile.com
mfns2.metafile.com
mfns3.metafile.com
mfns4.metafile.com

mfns2.metafile.com [108.62.121.219] (263ms):
mfns1.metafile.com
mfns2.metafile.com
mfns3.metafile.com
mfns4.metafile.com

mfns4.metafile.com [20.95.55.2] (175ms):
108.62.121.219
109.201.133.196
185.136.97.79
20.95.55.2
MFNS1.metafile.com
MFNS2.metafile.com
MFNS3.metafile.com
MFNS4.metafile.com

mfns1.metafile.com [109.201.133.196] (156ms):
mfns1.metafile.com
mfns2.metafile.com
mfns3.metafile.com
mfns4.metafile.com

mfns2.metafile.com [108.62.121.219] (222ms):
mfns1.metafile.com
mfns2.metafile.com
mfns3.metafile.com
mfns4.metafile.com

mfns4.metafile.com [20.95.55.2] (198ms):
108.62.121.219
109.201.133.196
185.136.97.79
20.95.55.2
MFNS1.metafile.com
MFNS2.metafile.com
MFNS3.metafile.com
MFNS4.metafile.com

Result: The NS records returned by the DNS servers are not the same as the name servers set at the parent server.
Recommendation: Check the synchronization between the DNS servers. Returned NS records must be exactly the same as these returned by the parent server.

3. SOA record

SOA record returned by each name server configured for the domain name

Frankfurt, DE

mfns1.metafile.com [109.201.133.196] (8ms):
public-dns1.metafile.com. support.cloudns.net. 2026042101 7200 1800 1209600 3600

mfns2.metafile.com [108.62.121.219] (87ms):
public-dns1.metafile.com. support.cloudns.net. 2026042101 7200 1800 1209600 3600

mfns4.metafile.com [20.95.55.2] (126ms):
Public-DNS1.metafile.com. hostmaster.metafile.com. 2026042101 43200 3600 2160000 600

San Francisco, US

mfns1.metafile.com [109.201.133.196] (144ms):
public-dns1.metafile.com. support.cloudns.net. 2026042101 7200 1800 1209600 3600

mfns2.metafile.com [108.62.121.219] (70ms):
public-dns1.metafile.com. support.cloudns.net. 2026042101 7200 1800 1209600 3600

mfns4.metafile.com [20.95.55.2] (40ms):
Public-DNS1.metafile.com. hostmaster.metafile.com. 2026042101 43200 3600 2160000 600

Sydney, AU

mfns1.metafile.com [109.201.133.196] (276ms):
public-dns1.metafile.com. support.cloudns.net. 2026042101 7200 1800 1209600 3600

mfns2.metafile.com [108.62.121.219] (267ms):
public-dns1.metafile.com. support.cloudns.net. 2026042101 7200 1800 1209600 3600

mfns4.metafile.com [20.95.55.2] (176ms):
Public-DNS1.metafile.com. hostmaster.metafile.com. 2026042101 43200 3600 2160000 600

Singapore

mfns1.metafile.com [109.201.133.196] (157ms):
public-dns1.metafile.com. support.cloudns.net. 2026042101 7200 1800 1209600 3600

mfns2.metafile.com [108.62.121.219] (219ms):
public-dns1.metafile.com. support.cloudns.net. 2026042101 7200 1800 1209600 3600

mfns4.metafile.com [20.95.55.2] (196ms):
Public-DNS1.metafile.com. hostmaster.metafile.com. 2026042101 43200 3600 2160000 600

Result: The SOA record returned by the name servers is not the same on all of them.
Recommendation: Check the synchronization between the DNS servers. Returned SOA record must be exactly the same on all DNS servers.

4. A record distribution by location for metaviewerap.com

Shows how the name servers respond to requests for metaviewerap.com

Frankfurt, DE San Francisco, US Sydney, AU Singapore

mfns1.metafile.com [109.201.133.196] (8ms):
35.214.157.53

mfns2.metafile.com [108.62.121.219] (89ms):
35.214.157.53

mfns4.metafile.com [20.95.55.2] (126ms):
35.214.157.53

mfns1.metafile.com [109.201.133.196] (142ms):
35.214.157.53

mfns2.metafile.com [108.62.121.219] (70ms):
35.214.157.53

mfns4.metafile.com [20.95.55.2] (40ms):
35.214.157.53

mfns1.metafile.com [109.201.133.196] (261ms):
35.214.157.53

mfns2.metafile.com [108.62.121.219] (265ms):
35.214.157.53

mfns4.metafile.com [20.95.55.2] (175ms):
35.214.157.53

mfns1.metafile.com [109.201.133.196] (156ms):
35.214.157.53

mfns2.metafile.com [108.62.121.219] (212ms):
35.214.157.53

mfns4.metafile.com [20.95.55.2] (196ms):
35.214.157.53

5. A record distribution by location for www.metaviewerap.com

Shows how the name servers respond to requests for www.metaviewerap.com

Frankfurt, DE San Francisco, US Sydney, AU Singapore

mfns1.metafile.com [109.201.133.196] (8ms):

mfns2.metafile.com [108.62.121.219] (92ms):

mfns4.metafile.com [20.95.55.2] (115ms):

mfns1.metafile.com [109.201.133.196] (141ms):

mfns2.metafile.com [108.62.121.219] (71ms):

mfns4.metafile.com [20.95.55.2] (43ms):

mfns1.metafile.com [109.201.133.196] (257ms):

mfns2.metafile.com [108.62.121.219] (278ms):

mfns4.metafile.com [20.95.55.2] (176ms):

mfns1.metafile.com [109.201.133.196] (158ms):

mfns2.metafile.com [108.62.121.219] (219ms):

mfns4.metafile.com [20.95.55.2] (196ms):

6. Speed

Result: During the checks in the previous steps, multiple DNS requests were executed to the name servers responsible for the domain name. Average response time of the name servers is 145.77ms.
Recommendation: The name servers respond slow. Try moving to an Anycast DNS service in order to speed up the resolution of the domain name and first page load of the web site.


Blog | Cloud DNS
Sponsored by ClouDNS