Veloga.co.kr Reviews

Veloga.co.kr has a total of 7 DNS records. In the server records, it appears to be registered with the IP address 52.231.38.95 in South Korea, Seoul, Seoul, Asia/Seoul with the information belonging to Microsoft Corporation The domain was registered on N/A, and the expiration date appears to be on N/A. When checked on , the website is still online. According to Siteadvisor, visiting veloga.co.kr is safe.

Location :
Seoul, South Korea πŸ‡°πŸ‡·
Last Checked: January 18, 2025
Server Status :
Online
Last Checked: January 18, 2025
Server :
Microsoft Corporation
Last Checked: January 18, 2025
Veloga.co.kr Screenshot

Robot.txt Information

Robot Path Permission
Google Bot /
Bing Bot /
Baudi Spider /
Yandex Bot /

Meta Tags

Title VELOGA :: Design your way
Description Drive, Ride, and Move with Veloga | 미래의 λͺ¨λ“  이동, λ²¨λ‘œκ°€μ™€ ν•¨κ»˜.
Keywords N/A

Server Information

Website veloga.co.kr
Host IP 52.231.38.95 πŸ‡°πŸ‡·
Location Seoul, South Korea

General Info - Legit or Scam?

Created N/A
Expires N/A
Owner N/A
Hosting Company Microsoft Corporation
Registrar N/A
IPs 52.231.38.95
DNS
  • ns.gabia.co.kr
  • ns1.gabia.co.kr
  • ns.gabia.net

DNS Records

Host Type TTL Data
veloga.co.kr A 600 IP/Target: 52.231.38.95
veloga.co.kr NS 86400 Target: ns.gabia.co.kr
veloga.co.kr NS 86400 Target: ns1.gabia.co.kr
veloga.co.kr NS 86400 Target: ns.gabia.net
veloga.co.kr CNAME 600
veloga.co.kr SOA 86400 MNAME: ns.gabia.co.kr
RNAME: hosting.gabia.com
Serial: 2021052115
Refresh: 1800
Retry: 600
Expire: 1209600
Minimum TTL: 86400
veloga.co.kr TXT 600 TXT: google-site-verification=kr-7OHM2BcxMLsAwDZe37FzZztNwUW6SECNmuu6vJYk

HTTP Headers

                                                    0: HTTP/1.1 200 OK
Connection: close
Content-Type: text/html; charset=UTF-8
Date: Sat, 18 Jan 2025 13:02:15 GMT
Server: nginx/1.26.1
X-Powered-By: PHP/8.2.21
                                                

Veloga.co.kr Whois Information

                                                    Error: Monthly quota exceeded. Consider upgrading your subscription or wait until the API renew date.