Oops.app valuation and analysis

Robots.txt Information
Robot Path Permission
GoogleBot /
BingBot /
BaiduSpider /
YandexBot /
Meta Tags
Title Oops
Description N/A
Keywords N/A
Server Information
WebSite oops favicon www.oops.app
Host IP 76.76.21.21
Location United States
Related Websites
Site Rank
More to Explore
osmangazieskort.xyz
oudigg191.top
over50sdating.net
pengkuanweb.top
pentanasolutions.com.au
peptidci.com
perforacionesjocal.com
pioneer-china.top
pizzatower.online
pkqg.cn
gruposancristobal.com.mx
gsm55.es
Oops.app Valuation
US$2,921
Last updated: Nov 12, 2023

Oops.app has global traffic rank of 28,567,440. Oops.app has an estimated worth of US$ 2,921, based on its estimated Ads revenue. Oops.app receives approximately 106 unique visitors each day. Its web server is located in United States, with IP address 76.76.21.21. According to SiteAdvisor, oops.app is unknown to visit.

Traffic & Worth Estimates
Purchase/Sale Value US$2,921
Daily Ads Revenue US$1
Monthly Ads Revenue US$48
Yearly Ads Revenue US$584
Daily Unique Visitors 106
Note: All traffic and earnings values are estimates.
Traffic Ranks
Global Rank 28,567,440
Delta (90 Days) 0
Most Popular In Country N/A
Country Rank N/A
DNS Records
Host Type TTL Data
oops.app A 300 IP: 76.76.21.21
oops.app MX 300 Priority: 10
Target: alt3.aspmx.l.google.com.
oops.app MX 300 Priority: 10
Target: alt4.aspmx.l.google.com.
oops.app MX 300 Priority: 5
Target: alt1.aspmx.l.google.com.
oops.app MX 300 Priority: 5
Target: alt2.aspmx.l.google.com.
oops.app MX 300 Priority: 1
Target: aspmx.l.google.com.
oops.app NS 21600 Target: maria.ns.cloudflare.com.
oops.app NS 21600 Target: jonah.ns.cloudflare.com.
oops.app TXT 300 TXT: new-relic-domain-verification=a38ffcf7ce1d4aeda367136167b0c2c1
oops.app TXT 300 TXT: v=spf1 include:_spf.google.com ~all
oops.app SOA 1800 MNAME: jonah.ns.cloudflare.com.
RNAME: dns.cloudflare.com.
Serial: 2325065538
Refresh: 10000
Retry: 2400
Expire: 604800
Minimum TTL: 1800
HTTP Headers
HTTP/1.0 308 Permanent Redirect
Content-Type: text/plain
Location: https://oops.app/
Refresh: 0;url=https://oops.app/
server: Vercel

HTTP/2 308 
cache-control: public, max-age=0, must-revalidate
content-type: text/plain
date: Sun, 12 Nov 2023 04:44:40 GMT
location: https://www.oops.app/
refresh: 0;url=https://www.oops.app/
server: Vercel
strict-transport-security: max-age=63072000
x-vercel-id: iad1::862bl-1699764280406-c64c3a6c7e0f

HTTP/2 200 
date: Sun, 12 Nov 2023 04:44:40 GMT
content-type: text/html; charset=utf-8
access-control-allow-origin: *
age: 14617645
cache-control: public, max-age=0, must-revalidate
content-disposition: inline
strict-transport-security: max-age=63072000
x-vercel-cache: HIT
x-vercel-id: iad1::skvql-1699764280524-23ed48a92c33
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=iAheqrPjWyqhj7H4WqKMFWnrkWWBCBKV5RcOJ%2BU7NjmUZZmnC13kPB2XpUjIB4HjOaA0EzVUGUEc%2FPbbxXFmsB4060fqBQxWTyfLLDwTIa9laOLgsrhIk4MCNFGIoVG67Ls9LtbCeVQ5eAY%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 824c1f010bc34392-EWR
alt-svc: h3=":443"; ma=86400

Oops.app Whois Information
Domain Name: oops.app
Registry Domain ID: 3B58F5030-APP
Registrar WHOIS Server: whois.google.com
Registrar URL: domains.google
Updated Date: 2023-04-26T01:55:40Z
Creation Date: 2019-07-27T02:20:45Z
Registry Expiry Date: 2024-07-27T02:20:45Z
Registrar: Squarespace Domains II LLC.
Registrar IANA ID: 895
Registrar Abuse Contact Email: registrar-abuse@google.com
Registrar Abuse Contact Phone: +1.8772376466
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Contact Privacy Inc. Customer 7151571251
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: ON
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: CA
Registrant Phone: REDACTED FOR PRIVACY
Registrant Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. 
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. 
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. 
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. 
Name Server: jonah.ns.cloudflare.com
Name Server: maria.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

Please query the WHOIS server of the owning registrar identified in this
output for information on how to contact the Registrant, Admin, or Tech
contact of the queried domain name.