It is not weird. It is the time it takes for DNS changes to propagate, compounded by the aggressive caching some browsers do. DNS changes can take up to a week to propagate. More if your browser is really hanging on to that cached version.
Here's one not DNS related:
404
https://www1.hitechcreations.com/styles/cp.css
https://www1.hitechcreations.com/styles/cp.css
Host: www1.hitechcreations.com
Accept: text/css,*/*;q=0.1
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Referer: https://www1.hitechcreations.com/
Connection: keep-alive
DNT: 1
GET: HTTP/1.1 404 Not Found
Date: Mon, 22 Oct 2018 16:46:14 GMT
Server: Apache/2.4.33 (Unix) OpenSSL/1.0.2p
X-Frame-Options: SAMEORIGIN
Cache-Control: no-cache
Pragma: no-cache
X-XSS-Protection: 1; mode=block
Content-Length: 1441
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
[/size][/font]
Here's one not DNS related:
404
https://www1.hitechcreations.com/styles/cp.css
https://www1.hitechcreations.com/styles/cp.css
Host: www1.hitechcreations.com
Accept: text/css,*/*;q=0.1
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Referer: https://www1.hitechcreations.com/
Connection: keep-alive
DNT: 1
GET: HTTP/1.1 404 Not Found
Date: Mon, 22 Oct 2018 16:46:14 GMT
Server: Apache/2.4.33 (Unix) OpenSSL/1.0.2p
X-Frame-Options: SAMEORIGIN
Cache-Control: no-cache
Pragma: no-cache
X-XSS-Protection: 1; mode=block
Content-Length: 1441
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
[/size][/font]
I need the full URL that came from.
https://www1.hitechcreations.com/ returns 200 and delivers a basically empty page with <meta HTTP-EQUIV="REFRESH" content="0; url=http://www.hitechcreations.com/index.php">. Its freshly delivered, not cached. Might be from the wrong server if www1.hitechcreations.com isn't 199.101.50.180 of course.
The only error I see here is a redirect to a non-secure URL. I'll check that.