Solutions for your inquiries

  hosting
<< Back       health mail

Question: Good afternoon. Please check and if possible recover with the email in our account. Symptoms: new mail arrives, the sender side the error message cannot connect to host, outgoing mail works through time (for example, on gmail emails coming into other domains - no)
Answer:

Hello.

the Question referred to the administrator, wait for amp.

Question: Hey, guys!? ;-)
Answer:

tazovoe send email to service mail-tester.com and provide a link to the result

Question: https://www.mail-tester.com/web-2uhcc
Answer:

the problem is checked

 

Question: good question. what is it? over the past half year changes, personally, I have no not made. Passwords from accounts is not only for me, but hardly anyone was snooping around in here. Than it can threaten? can I restore them?
Answer:


please Do a trace to Your domain: start - run - enter cmd - in the black window enter tracert YOUR DOMAIN - after click to highlight - making enter - skopirovat here in the ticket

If You are experiencing zatrudina, view instructional videos http://ded07.net/helphost/tracert.htm

Question: C:\\Users\\*****>tracert sk-vector.aggressive route to sk-vector.org [209.99.40.221]with the maximum number of jumps 30: 1 2 ms 3 ms 1 ms 192.168.1.1 2 3 ms 3 ms 1 ms 78.107.145.21 3 2 ms 3 ms 2 ms marino-bng2-local.msk.corbina.net [85.21.0.218] 4 3 ms 3 ms 5 ms 10.2.251.46 5 4 ms 3 ms 3 ms varsh172-bb-be4.corbina.net [195.14.54.123] 6 4 ms 4 ms 3 ms lesnor-bb-be7.corbina.net [195.14.51.57] 7 23 ms 23 ms 21 ms lesnor-bb-dpi-out.corbina.net [213.234.211.114] 8 21 ms 23 ms 23 ms ko-crs-be5.corbina.net [195.14.54.184] 9 22 ms 21 ms 21 ms tc-bb-telia-loop.corbina.net [85.21.1.45] 10 21 ms 21 ms 22 ms beeline-gw4.bar1.Stockholm1.Level3.net [213.242.110.105] 11 21 ms 22 ms 21 ms be3045.ccr21.sto01.atlas.cogentco.com [130.117.14.5] 12 23 ms 22 ms 30 ms be2397.ccr22.sto03.atlas.cogentco.com [130.117.50.129] 13 51 ms 51 ms 51 ms be2282.ccr42.ham01.atlas.cogentco.com [154.54.72.105] 14 52 ms 56 ms 48 ms be2816.ccr42.ams03.atlas.cogentco.com [154.54.38.209] 15 125 ms 126 ms 126 ms be12488.ccr42.lon13.atlas.cogentco.com [130.117.51.41] 16 127 ms 125 ms 123 ms be2983.ccr22.bos01.atlas.cogentco.com [154.54.1.178] 17 123 ms 125 ms 123 ms be2096.ccr42.jfk02.atlas.cogentco.com [154.54.30.41] 18 132 ms 133 ms 132 ms be2807.ccr42.dca01.atlas.cogentco.com [154.54.40.110] 19 143 ms 144 ms 143 ms be2113.ccr42.atl01.atlas.cogentco.com [154.54.24.222] 20 163 ms 166 ms 163 ms be2690.ccr22.iah01.atlas.cogentco.com [154.54.28.130] 21 167 ms 166 ms 169 ms be2874.rcr12.aus02.atlas.cogentco.com [154.54.6.54] 22 167 ms 167 ms 169 ms te0-0-2-3.nr11.b006628-1.aus02.atlas.cogentco.com [154.24.30.254] 23 169 ms 168 ms 169 ms 38.122.254.14 24 166 ms 166 ms 166 ms 209-99-40-221.fwd.datafoundry.com [209.99.40.221]Trace complete.
Answer:

judging by the traceroute problem at the Registrar. we otpravili request


<< Back