J-fest.org Reviews

J-fest.org has a total of 9 DNS records. In the server records, it appears to be registered with the IP address 87.236.16.99 in Russia, St.-Petersburg, St Petersburg, Europe/Moscow with the information belonging to BEGET.RU 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 j-fest.org is safe.

Location :
St Petersburg, Russia 🇷🇺
Last Checked: December 04, 2024
Server Status :
Online
Last Checked: December 04, 2024
Server :
BEGET.RU
Last Checked: December 04, 2024
J-fest.org Screenshot

Robot.txt Information

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

Meta Tags

Title N/A
Description N/A
Keywords N/A

Server Information

Website j-fest.org
Host IP 87.236.16.99 🇷🇺
Location St Petersburg, Russia

General Info - Legit or Scam?

Created N/A
Expires N/A
Owner N/A
Hosting Company BEGET.RU
Registrar N/A
IPs 87.236.16.99
DNS
  • ns1.beget.com
  • ns2.beget.com
  • ns1.beget.pro
  • ns2.beget.pro

DNS Records

Host Type TTL Data
j-fest.org A 600 IP/Target: 87.236.16.99
j-fest.org NS 300 Target: ns1.beget.com
j-fest.org NS 300 Target: ns2.beget.com
j-fest.org NS 300 Target: ns1.beget.pro
j-fest.org NS 300 Target: ns2.beget.pro
j-fest.org SOA 300 MNAME: ns1.beget.com
RNAME: hostmaster.beget.com
Serial: 1640777413
Refresh: 300
Retry: 600
Expire: 86400
Minimum TTL: 300
j-fest.org MX 300 IP/Target: mx1.beget.com
j-fest.org MX 300 IP/Target: mx2.beget.com
j-fest.org TXT 300 TXT: v=spf1 redirect=beget.com

HTTP Headers

                                                    0: HTTP/1.1 200 OK
Server: nginx-reuseport/1.21.1
Date: Wed, 04 Dec 2024 14:37:04 GMT
Content-Type: text/html
Content-Length: 274
Last-Modified: Wed, 14 Feb 2018 17:24:40 GMT
Connection: close
ETag: "5a8470d8-112"
Accept-Ranges: bytes
                                                

J-fest.org Whois Information

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