Safehaven.io Web Analysis and Statistics
Website Summary
-
When was the website Safehaven.io released?
Safehaven.io was registered on November 4, 2017 (7 years 12 days ago).
-
What is the traffic rank for Safehaven.io?
Website Safehaven.io ranked 2,232,488 globally and 280,693 in United States.
-
How many people visit Safehaven.io each day?
Safehaven.io has about 210 visits and 280 pageviews per day.
-
How much does Safehaven.io earn a month?
Each month Safehaven.io can earn $23 from advertising revenue.
-
How much is Safehaven.io worth?
Estimated value of Safehaven.io is $140
-
What IP addresses does Safehaven.io resolve to?
Safehaven.io resolves to the IP addresses 104.21.7.30
-
Where is Safehaven.io server located?
Safehaven.io's server is located in California, San Francisco, United States Of America, 94107.
-
Who is registrar of Safehaven.io domain?
The safehaven.io domain is registered and managed by Key-Systems GmbH
Safehaven.io's metrics:
- Global traffic rank:
- 2,232,488
- Traffic rank in United States:
- 280,693
- Daily income:
- $0.76
- Estimated Worth:
- $140
- Website category:
- Business
- Safety status:
- Safe
HTML Analysis
HTML Meta tags:
Title: Safe Haven - Building Decentralized Finance (DeFi) Solutions since 2017
Description: Safe Haven builds DeFi solutions for safely managing, storing & transferring crypto or digital assets like NFTs, passwords, documents, etc.
Logo:
HTML elements:
- H1 Headings:
- 1
- H2 Headings:
- 2
- H3 Headings:
- 2
- H4 Headings:
- 1
- H5 Headings:
- 13
- H6 Headings:
- 0
- Total Images:
- 285
- Total IFRAMEs:
- 1
Links analysis:
- Total links:
- 133
- Internal links:
- 34
- Internal links (nofollow):
- 0
- External links:
- 32
- External links (nofollow):
- 0
HTTP Header:
Http-Version: 1.1
Status-Code: 200
Status: 200 OK
Date: Sat, 19 Aug 2023 07:19:41 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
cf-edge-cache: cache, platform=WordPress
x-content-type-options: nosniff
referrer-policy: strict-origin-when-cross-origin
permissions-policy: geolocation 'self'; midi 'self'; sync-xhr 'self'; microphone 'self'; camera 'self'; magnetometer 'self'; gyroscope 'self'; speaker 'self'; fullscreen 'self'; payment 'self';
link:
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=/aDmV/NbtuedAWcaFFH6YlWChcktb4QYlrAKuRHtRbLHt2DJwjBpEWReScq9GKzKvP6UJfxX+JfiFLgC+I+D0cfZVVApq4FWPfLbCPjVEJync4ENKIcrvCIwaA633/jIL9Jhi9h4dJ0TjiA="}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Strict-Transport-Security: max-age=15552000; includeSubDomains; preload
Server: cloudflare
CF-RAY: 7f90a1279f333b59-IAD
Content-Encoding: gzip
alt-svc: h3=":443"; ma=86400
Safehaven.io Traffic Analysis
- Daily unique visitors:
- 210
- Daily pageviews:
- 280
- Daily pageviews per visitor:
- 1.3
- Monthly visits:
- 6,300
- Annual visits:
- 76,650
Safehaven.io SSL Certificate Information
Common name: safehaven.io
SANs: safehaven.io, *.safehaven.io
Organization: Cloudflare, Inc.
Location: San Francisco, California, US
Serial Number: 056439E116E6089D37E48966C8150E1C
Signature Algorithm: ecdsa-with-SHA256
Issuer: Cloudflare Inc ECC CA-3
Fingerprint: 7414f86659738131a7fc6d3c2c5001bb352c78d4
FingerprintSha256: 3ebc7a847c8227de9b285ad4cea47bb7dec2fd515f1387159ae3adc511196b84
Safehaven.io Domain Name Information
- Domain TLD:
- io
- Domain Registrar:
- Key-Systems GmbH
- Registration Date:
- November 4, 2017
- Expiration Date:
- November 4, 2023
- Domain Age:
- 7 years 12 days
- Domain Status:
- ok
Domain Nameserver Information:
Full WHOIS Lookup:
Registry Domain ID: 497c36051a2540b0a6bc171bfb247f15-DONUTS
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL: http://key-systems.net
Updated Date: 2022-12-19T22:11:13Z
Creation Date: 2017-11-04T22:10:51Z
Registry Expiry Date: 2023-11-04T22:10:51Z
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +49 6894 9396 850
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization:
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province:
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: BE
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record 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 Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record 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 Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: jack.ns.cloudflare.com
Name Server: grace.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-08-19T07:19:37Z
Safehaven.io Server Information
- Server IP Address:
- 104.21.7.30
- Hosted Country:
- πΊπΈ United States
- Latitude, longitude:
- 37.7757 , -122.395
- Location:
- California, San Francisco, United States Of America, 94107
DNS Record Analysis:
RNAME: dns.cloudflare.com
Serial: 2286791670
Refresh: 10000
Retry: 2400
Expire: 604800
Minimum TTL: 3600
Target: mx.backup.mailprotect.be
Target: mx.mailprotect.be
Typos of Safehaven.io
Sometimes, misspellings make a good domain name. And spelling errors are also a great way to create keywords for SEO. And the following are all possible typos of Safehaven.io. You can use them for competitive domain name search or for SEO strategies for Safehaven.io:
- aafehaven.io
- zafehaven.io
- xafehaven.io
- dafehaven.io
- eafehaven.io
- wafehaven.io
- szfehaven.io
- ssfehaven.io
- swfehaven.io
- sqfehaven.io
- sadehaven.io
- sacehaven.io
- savehaven.io
- sagehaven.io
- satehaven.io
- sarehaven.io
- safwhaven.io
- safshaven.io
- safdhaven.io
- safrhaven.io
- saf4haven.io
- saf3haven.io
- safegaven.io
- safebaven.io
- safenaven.io
- safejaven.io
- safeuaven.io
- safeyaven.io
- safehzven.io
- safehsven.io
- safehwven.io
- safehqven.io
- safehacen.io
- safehaben.io
- safehagen.io
- safehafen.io
- safehavwn.io
- safehavsn.io
- safehavdn.io
- safehavrn.io
- safehav4n.io
- safehav3n.io
- safehaveb.io
- safehavem.io
- safehavej.io
- safehaveh.io
- afehaven.io
- sfehaven.io
- saehaven.io
- safhaven.io
- safeaven.io
- safehven.io
- safehaen.io
- safehavn.io
- safehave.io
- asfehaven.io
- sfaehaven.io
- saefhaven.io
- safheaven.io
- safeahven.io
- safehvaen.io
- safehaevn.io
- safehavne.io
- ssafehaven.io
- saafehaven.io
- saffehaven.io
- safeehaven.io
- safehhaven.io
- safehaaven.io
- safehavven.io
- safehaveen.io
- safehavenn.io
Thank you for reading our analysis & statistics about Safehaven.io website. If you find it interesting, please share it with your friends. If you have any suggestions, please comment below or contact us.