Lykke.com Reviews

Lykke.com has a total of 18 DNS records. In the server records, it appears to be registered with the IP address 76.76.21.21 in United States, California, Walnut, America/Los_Angeles with the information belonging to Amazon.com, 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 lykke.com is safe.

Location :
Walnut, United States 🇺🇸
Last Checked: November 30, 2024
Server Status :
Online
Last Checked: November 30, 2024
Server :
Amazon.com, Inc.
Last Checked: November 30, 2024
Lykke.com Screenshot

Robot.txt Information

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

Meta Tags

Title No Fee Crypto Exchange | Lykke
Description Lykke is a fintech company that runs a 0-fee crypto exchange and provides blockchain solutions for businesses
Keywords N/A

Server Information

Website lykke.com
Host IP 76.76.21.21 🇺🇸
Location Walnut, United States

General Info - Legit or Scam?

Created N/A
Expires N/A
Owner N/A
Hosting Company Amazon.com, Inc.
Registrar N/A
IPs 76.76.21.21
DNS
  • josh.ns.cloudflare.com
  • may.ns.cloudflare.com

DNS Records

Host Type TTL Data
lykke.com A 300 IP/Target: 76.76.21.21
lykke.com NS 86400 Target: josh.ns.cloudflare.com
lykke.com NS 86400 Target: may.ns.cloudflare.com
lykke.com SOA 1800 MNAME: josh.ns.cloudflare.com
RNAME: dns.cloudflare.com
Serial: 2355822780
Refresh: 10000
Retry: 2400
Expire: 604800
Minimum TTL: 1800
lykke.com MX 300 IP/Target: aspmx2.googlemail.com
lykke.com MX 300 IP/Target: aspmx3.googlemail.com
lykke.com MX 300 IP/Target: aspmx.l.google.com
lykke.com MX 300 IP/Target: alt1.aspmx.l.google.com
lykke.com MX 300 IP/Target: mail.lykke.com
lykke.com MX 300 IP/Target: alt2.aspmx.l.google.com
lykke.com TXT 300 TXT: google-site-verification=lSZIxtJjlU7co7XNtwezzjmtHxPKEVzN2oGhvtVL9Ec
lykke.com TXT 300 TXT: google-site-verification=vsiZbAgMrOl0y_GTqIzTSpOlX5zuMwcBvmlOPXdBAXs
lykke.com TXT 300 TXT: lykke-qr.azurewebsites.net
lykke.com TXT 300 TXT: ts13l2cdmrxfpbqzskt8zcsxdtc0zy8j
lykke.com TXT 300 TXT: v=spf1 include:_spf.mlsend.com include:_spf.google.com include:mail.zendesk.com include:amazonses.com -all
lykke.com TXT 300 TXT: MS=ms66870555
lykke.com TXT 300 TXT: facebook-domain-verification=o1ron3k1q72ps8ei19hak480fm1dlq
lykke.com TXT 300 TXT: google-site-verification=0rNPt4-dfbGNDh2kPQD_yanG7R-itPL58nGSXgxbUSg

HTTP Headers

                                                    0: HTTP/1.0 308 Permanent Redirect
Cache-Control: ["public, max-age=0, must-revalidate","public, max-age=0, must-revalidate"]
Content-Type: ["text\/plain","text\/html; charset=utf-8"]
Date: ["Sat, 30 Nov 2024 10:44:03 GMT","Sat, 30 Nov 2024 10:44:04 GMT"]
Location: https://www.lykke.com/
Refresh: 0;url=https://www.lykke.com/
Server: ["Vercel","cloudflare"]
Strict-Transport-Security: max-age=63072000
X-Vercel-Id: cdg1::zkfkk-1732963443952-796603049f74
1: HTTP/1.1 200 OK
Connection: close
Age: 175293
strict-transport-security: max-age=63072000
vary: RSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Url
x-matched-path: /
x-powered-by: Next.js
x-vercel-cache: HIT
x-vercel-id: cdg1::fra1::8dgsp-1732963444041-27ea15b2775f
CF-Cache-Status: DYNAMIC
Report-To: {
    "endpoints": [
        {
            "url": "https://a.nel.cloudflare.com/report/v4?s=A8P7%2F2rP6k6nHPtq%2BcJZqOJp5XesUIkcvPAgVJ2lJZwSPyC%2Famz%2Ba5f66N6irI5spL5lAIAiWIJgE53C%2FnmmM890y7cvvG123I1dP74JlxyqFtSSeRlVBg2189tK0zQ%3D"
        }
    ],
    "group": "cf-nel",
    "max_age": 604800
}
NEL: {
    "success_fraction": 0,
    "report_to": "cf-nel",
    "max_age": 604800
}
CF-RAY: 8eaa3d750c14d397-CDG
server-timing: cfL4;desc="?proto=TCP&rtt=5327&min_rtt=5234&rtt_var=1274&sent=5&recv=7&lost=0&retrans=0&sent_bytes=2505&recv_bytes=730&delivery_rate=479152&cwnd=191&unsent_bytes=0&cid=2546dbfea6408aec&ts=129&x=0"
                                                

Lykke.com Whois Information

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