Sunadokei.party has a total of 11 DNS records. In the server records, it appears to be registered with the IP address 159.89.138.96 in United States, California, Santa Clara, America/Los_Angeles with the information belonging to DigitalOcean, LLC 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 sunadokei.party is safe.
Robot | Path | Permission |
---|---|---|
Google Bot | / | |
Bing Bot | / | |
Baudi Spider | / | |
Yandex Bot | / |
Title | Welcome to nginx! |
Description | N/A |
Keywords | N/A |
Website | sunadokei.party |
Host IP | 159.89.138.96 🇺🇸 |
Location | Santa Clara, United States |
Created | N/A |
Expires | N/A |
Owner | N/A |
Hosting Company | DigitalOcean, LLC |
Registrar | N/A |
IPs | 159.89.138.96 |
DNS |
|
Host | Type | TTL | Data |
---|---|---|---|
sunadokei.party | A | 1800 | IP/Target: 159.89.138.96 |
sunadokei.party | NS | 1800 | Target: dns1.registrar-servers.com |
sunadokei.party | NS | 1800 | Target: dns2.registrar-servers.com |
sunadokei.party | SOA | 3601 |
MNAME: dns1.registrar-servers.com RNAME: hostmaster.registrar-servers.com Serial: 1650317922 Refresh: 43200 Retry: 3600 Expire: 604800 Minimum TTL: 3601 |
sunadokei.party | MX | 1800 | IP/Target: eforward4.registrar-servers.com |
sunadokei.party | MX | 1800 | IP/Target: eforward1.registrar-servers.com |
sunadokei.party | MX | 1800 | IP/Target: eforward2.registrar-servers.com |
sunadokei.party | MX | 1800 | IP/Target: eforward3.registrar-servers.com |
sunadokei.party | MX | 1800 | IP/Target: eforward5.registrar-servers.com |
sunadokei.party | TXT | 1800 | TXT: v=spf1 include:spf.efwd.registrar-servers.com ~all |
sunadokei.party | AAAA | 1800 | Ipv6: 2604:a880:2:d0::8b0:e001 |
0: HTTP/1.1 200 OK Server: nginx/1.18.0 Date: Sat, 01 Feb 2025 23:11:04 GMT Content-Type: text/html Content-Length: 612 Last-Modified: Tue, 21 Apr 2020 14:09:01 GMT Connection: close ETag: "5e9efe7d-264" Accept-Ranges: bytes |
Error: Monthly quota exceeded. Consider upgrading your subscription or wait until the API renew date. |