forklog.ru - dns.ninja
forklog.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 45.82.31.247🇰🇿 GCORE45.82.31.0/24 GCL-45-82-31-0-24 | ||||||
| NS | ns1.digitalocean.com ⭐ ⚠️ Not in zone NS records | ||||||
| A | 2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| A | 172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| NS | ns2.digitalocean.com ⚠️ Not in zone NS records | ||||||
| A | 2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| A | 172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| NS | ns3.digitalocean.com ⚠️ Not in zone NS records | ||||||
| A | 2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| A | 172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| SOA | ns1.digitalocean.comhostmaster@forklog.ru serial=0 | ||||||
ru
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | c.tld-servers.ru | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=4069675 | ||||||
Same first word
Similar names
DNS History
8 records (4 active, 4 former)
●NSns1.digitalocean.com2026-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:34:44
●NSns2.digitalocean.com2026-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:34:44
●NSns3.digitalocean.com2026-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:34:44
○A128.199.46.232018-05-09 → 2018-05-09 · 2 obs
○ 2026-07-19 21:34:44
●A45.82.31.2472026-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 21:34:44
○A46.101.169.752026-07-19 → 2026-07-19 · 1 obs
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net... | - |
| forklog.ru | ns1.digitalocean.com, ns3.digitalocean.com, ns2.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns1.digitalocean.com, ns3.digitalocean.com, ns2.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for forklog.ru (unsigned zone)
⏱️ Timing
Total: 662ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.82.31.247 |
| SOA | 1 | ns1.digitalocean.com hostmaster.forklog. |
Analysis
IP Addresses
forklog.ru has exactly one IP address — 45.82.31.247.
Other host names share IP numbers with forklog.ru; forklog.com is one such example.
Name Servers
Three name servers are authoritative for forklog.ru: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
There is at least partial name server overlap between forklog.ru and other domains — ohvids.com, playcasinoww.com, bjb.is and two more among them.
ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2. ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515. ns3.digitalocean.com resolves to 172.64.49.209 and 2606:4700:52::ac40:31d1. All three hostnames point to two IP numbers each.