Flatulencecures.com Reviews

Flatulencecures.com has a total of 19 DNS records. In the server records, it appears to be registered with the IP address 104.21.80.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 flatulencecures.com is safe.

Location :
Toronto, Canada 🇨🇦
Last Checked: December 26, 2024
Server Status :
Online
Last Checked: December 26, 2024
Server :
Cloudflare, Inc.
Last Checked: December 26, 2024
Flatulencecures.com Screenshot

Robot.txt Information

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

Meta Tags

Title Flatulence Cures: Natural Remedies For Gas And Bloating
Description How to quickly fix excessive flatulence, belly bloat, intestinal cramps, an upset stomach and other digestive problems with potent natural cures
Keywords N/A

Server Information

Website flatulencecures.com
Host IP 104.21.80.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.80.1
DNS
  • kurt.ns.cloudflare.com
  • nia.ns.cloudflare.com

DNS Records

Host Type TTL Data
flatulencecures.com A 300 IP/Target: 104.21.80.1
flatulencecures.com A 300 IP/Target: 104.21.96.1
flatulencecures.com A 300 IP/Target: 104.21.16.1
flatulencecures.com A 300 IP/Target: 104.21.112.1
flatulencecures.com A 300 IP/Target: 104.21.64.1
flatulencecures.com A 300 IP/Target: 104.21.32.1
flatulencecures.com A 300 IP/Target: 104.21.48.1
flatulencecures.com NS 86400 Target: kurt.ns.cloudflare.com
flatulencecures.com NS 86400 Target: nia.ns.cloudflare.com
flatulencecures.com SOA 1800 MNAME: kurt.ns.cloudflare.com
RNAME: dns.cloudflare.com
Serial: 2356520137
Refresh: 10000
Retry: 2400
Expire: 604800
Minimum TTL: 1800
flatulencecures.com MX 300 IP/Target: _dc-mx.4e8c6cf20745.flatulencecures.com
flatulencecures.com TXT 300 TXT: v=spf1 a mx a:flatulencecures.com ip4:67.202.92.17 ?all
flatulencecures.com AAAA 300 Ipv6: 2606:4700:3030::6815:3001
flatulencecures.com AAAA 300 Ipv6: 2606:4700:3030::6815:2001
flatulencecures.com AAAA 300 Ipv6: 2606:4700:3030::6815:4001
flatulencecures.com AAAA 300 Ipv6: 2606:4700:3030::6815:7001
flatulencecures.com AAAA 300 Ipv6: 2606:4700:3030::6815:5001
flatulencecures.com AAAA 300 Ipv6: 2606:4700:3030::6815:1001
flatulencecures.com AAAA 300 Ipv6: 2606:4700:3030::6815:6001

HTTP Headers

                                                    0: HTTP/1.1 200 OK
Date: Thu, 26 Dec 2024 22:49:03 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
x-powered-by: PHP/8.2.26
cf-edge-cache: cache,platform=wordpress
link: ["; rel=\"https:\/\/api.w.org\/\"","; rel=\"alternate\"; title=\"JSON\"; type=\"application\/json\""]
vary: Accept-Encoding,User-Agent
wpx: 1
x-xss-protection: 1; mode=block
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
strict-transport-security: max-age=63072000; includeSubDomains
referrer-policy: no-referrer-when-downgrade
alt-svc: h3=":443"; ma=86400
x-turbo-charged-by: LiteSpeed
Last-Modified: Thu, 26 Dec 2024 21:07:03 GMT
CF-Cache-Status: HIT
Age: 5279
Report-To: {
    "endpoints": [
        {
            "url": "https://a.nel.cloudflare.com/report/v4?s=%2BnLoS2DVWDB6EK1HxA835QlRa1h1J8Db2tpcPEz4DU4oLxLk6WmBT6ppxKJ3wtDuhfthLiVjGPCxN%2FntJ1OvJt9l9YG2r0Vekg5GEf6AUX6vzFWgT8sGgoy8rcOmT1ZZsM0gfGby"
        }
    ],
    "group": "cf-nel",
    "max_age": 604800
}
NEL: {
    "success_fraction": 0,
    "report_to": "cf-nel",
    "max_age": 604800
}
Server: cloudflare
CF-RAY: 8f849f351ae2660f-AMS
server-timing: cfL4;desc="?proto=TCP&rtt=7596&min_rtt=7518&rtt_var=2166&sent=4&recv=6&lost=0&retrans=0&sent_bytes=3022&recv_bytes=736&delivery_rate=385208&cwnd=252&unsent_bytes=0&cid=f9f9727b8ccec121&ts=39&x=0"
                                                

Flatulencecures.com Whois Information

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