Your problem is very likely that the two name servers in use by your domain (NS75.DOMAINCONTROL.COM and NS76.DOMAINCONTROL.COM) are each handing out a different IP when queried for your domain. See the DIG results below for proof. In short, NS75.DOMAINCONTROL.COM is handing out 184.168.221.2 while NS76.DOMAINCONTROL.COM is handing out 50.63.202.5. My advice is to show the DIG results below to Godaddy and ask why their 2 name servers are handing out different IPs as this is very uncommon and typically indicative of a problem.
Regarding which IP to use, 199.34.228.55 is an IP from Weebly's system (they have several IPs). You will want to ask Weebly which IP is correct for you since I believe only certain IPs are used for https if you require that and have it configured.
Here are the dig results:
dig a xn--e5h.com @NS75.DOMAINCONTROL.COM
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.4 <<>> a xn--e5h.com @NS75.DOMAINCONTROL.COM
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32871
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;â.com. IN A
;; ANSWER SECTION:
â.com. 600 IN A 184.168.221.2
;; AUTHORITY SECTION:
â.com. 3600 IN NS ns76.domaincontrol.com.
â.com. 3600 IN NS ns75.domaincontrol.com.
-------------------------------------------------
dig a xn--e5h.com @NS76.DOMAINCONTROL.COM
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.4 <<>> a xn--e5h.com @NS76.DOMAINCONTROL.COM
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29986
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;â.com. IN A
;; ANSWER SECTION:
â.com. 600 IN A 50.63.202.5
;; AUTHORITY SECTION:
â.com. 3600 IN NS ns76.domaincontrol.com.
â.com. 3600 IN NS ns75.domaincontrol.com.