Junkybooks.com Reviews

Junkybooks.com has a total of 10 DNS records. In the server records, it appears to be registered with the IP address 172.67.208.173 in Canada, Ontario, Toronto, America/Toronto with the information belonging to Cloudflare, Inc. 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 junkybooks.com is safe.

Location :
Toronto, Canada 🇨🇦
Last Checked: January 15, 2025
Server Status :
Offline
Last Checked: N/A
Server :
Cloudflare, Inc.
Last Checked: January 15, 2025
Junkybooks.com 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 junkybooks.com
Host IP 172.67.208.173 🇨🇦
Location Toronto, Canada

General Info - Legit or Scam?

Created N/A
Expires N/A
Owner N/A
Hosting Company Cloudflare, Inc.
Registrar N/A
IPs 172.67.208.173
DNS
  • peyton.ns.cloudflare.com
  • zara.ns.cloudflare.com

DNS Records

Host Type TTL Data
junkybooks.com A 300 IP/Target: 172.67.208.173
junkybooks.com A 300 IP/Target: 104.21.85.175
junkybooks.com NS 86400 Target: peyton.ns.cloudflare.com
junkybooks.com NS 86400 Target: zara.ns.cloudflare.com
junkybooks.com SOA 1800 MNAME: peyton.ns.cloudflare.com
RNAME: dns.cloudflare.com
Serial: 2360090342
Refresh: 10000
Retry: 2400
Expire: 604800
Minimum TTL: 1800
junkybooks.com MX 300 IP/Target: _dc-mx.17cf52f4d232.junkybooks.com
junkybooks.com MX 300 IP/Target: _dc-mx.e9b7b2a06593.junkybooks.com
junkybooks.com TXT 300 TXT: v=spf1 +a +mx +ip4:209.74.64.151 ~all
junkybooks.com AAAA 300 Ipv6: 2606:4700:3030::6815:55af
junkybooks.com AAAA 300 Ipv6: 2606:4700:3033::ac43:d0ad

HTTP Headers

                                                    N/A                                                

Junkybooks.com Whois Information

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