Fencing.net Reviews

Fencing.net has a total of 24 DNS records. In the server records, it appears to be registered with the IP address 104.21.48.1 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 fencing.net is safe.

Location :
Toronto, Canada 🇨🇦
Last Checked: January 20, 2025
Server Status :
Online
Last Checked: January 20, 2025
Server :
Cloudflare, Inc.
Last Checked: January 20, 2025
Fencing.net Screenshot

Robot.txt Information

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

Meta Tags

Title Fencing news, guides and equipment reviews - Fencing.Net
Description N/A
Keywords N/A

Server Information

Website fencing.net
Host IP 104.21.48.1 🇨🇦
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 104.21.48.1
DNS
  • rob.ns.cloudflare.com
  • nia.ns.cloudflare.com

DNS Records

Host Type TTL Data
fencing.net A 300 IP/Target: 104.21.48.1
fencing.net A 300 IP/Target: 104.21.80.1
fencing.net A 300 IP/Target: 104.21.32.1
fencing.net A 300 IP/Target: 104.21.16.1
fencing.net A 300 IP/Target: 104.21.96.1
fencing.net A 300 IP/Target: 104.21.112.1
fencing.net A 300 IP/Target: 104.21.64.1
fencing.net NS 86400 Target: rob.ns.cloudflare.com
fencing.net NS 86400 Target: nia.ns.cloudflare.com
fencing.net SOA 1800 MNAME: nia.ns.cloudflare.com
RNAME: dns.cloudflare.com
Serial: 2362663826
Refresh: 10000
Retry: 2400
Expire: 604800
Minimum TTL: 1800
fencing.net MX 300 IP/Target: alt1.aspmx.l.google.com
fencing.net MX 300 IP/Target: alt2.aspmx.l.google.com
fencing.net MX 300 IP/Target: aspmx.l.google.com
fencing.net MX 300 IP/Target: alt3.aspmx.l.google.com
fencing.net MX 300 IP/Target: alt4.aspmx.l.google.com
fencing.net TXT 300 TXT: v=spf1 ip4:185.17.182.16 include:_spf.google.com ~all
fencing.net TXT 300 TXT: google-site-verification=TeoQd6pWqYV6CrzKpNOVitfC1YCEx_cqhGcYVQetA9Y
fencing.net AAAA 300 Ipv6: 2606:4700:3030::6815:4001
fencing.net AAAA 300 Ipv6: 2606:4700:3030::6815:5001
fencing.net AAAA 300 Ipv6: 2606:4700:3030::6815:7001
fencing.net AAAA 300 Ipv6: 2606:4700:3030::6815:2001
fencing.net AAAA 300 Ipv6: 2606:4700:3030::6815:3001
fencing.net AAAA 300 Ipv6: 2606:4700:3030::6815:1001
fencing.net AAAA 300 Ipv6: 2606:4700:3030::6815:6001

HTTP Headers

                                                    0: HTTP/1.1 200 OK
Date: Mon, 20 Jan 2025 20:32:05 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
vary: Accept-Encoding
link: ["; rel=\"https:\/\/api.w.org\/\"","; rel=\"alternate\"; title=\"JSON\"; type=\"application\/json\"","; rel=shortlink"]
expires: Mon, 20 Jan 2025 20:32:05 GMT
Cache-Control: max-age=0
x-cache-status: HIT
x-rocket-nginx-serving-static: MISS
strict-transport-security: max-age=31536000;
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
referrer-policy: no-referrer-when-downgrade
content-security-policy: default-src * 'unsafe-inline' 'unsafe-eval' data: blob:;
cf-cache-status: DYNAMIC
Report-To: {
    "endpoints": [
        {
            "url": "https://a.nel.cloudflare.com/report/v4?s=xn5tMsDSMDtlYqPm3Fcr9VeFTgO8gw30ubG5H2wkBDWDSy1989tqy9tNWpd64jTJ8Pjast5G%2BIjT0B9MTQZ6lIhOowplmBl%2BGQcIeOBVbhFdx94B66MatWRpl17SFA%3D%3D"
        }
    ],
    "group": "cf-nel",
    "max_age": 604800
}
NEL: {
    "success_fraction": 0,
    "report_to": "cf-nel",
    "max_age": 604800
}
Server: cloudflare
CF-RAY: 9051d4f02a72f5f3-AMS
alt-svc: h3=":443"; ma=86400
server-timing: cfL4;desc="?proto=TCP&rtt=6132&min_rtt=6016&rtt_var=1759&sent=5&recv=6&lost=0&retrans=0&sent_bytes=2998&recv_bytes=728&delivery_rate=481382&cwnd=252&unsent_bytes=0&cid=6f674b9d932c1d1a&ts=224&x=0"
                                                

Fencing.net Whois Information

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