forklog.com - dns.ninja
forklog.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1784456437 | ||||||
rank #14313 in the tld
WOT: SAFE (89/100)
📈 Tranco rank: #86,176
Same first word
Similar names
DNS History
20 records (8 active, 12 former)
○NSdns1.yandex.net2016-12-05 → 2017-02-17 · 4 obs
● 2017-02-17 07:26:08
○ 2017-12-13 06:42:30
○ 2026-07-19 10:36:50
○NSdns2.yandex.net2016-12-05 → 2017-02-17 · 4 obs
● 2017-02-17 07:26:08
○ 2017-12-13 06:42:30
○ 2026-07-19 10:36:50
○NSns1.digitalocean.com2017-12-13 → 2021-09-26 · 5 obs
● 2017-12-13 06:42:30
● 2021-09-26 12:18:30
○ 2026-07-19 10:36:48
○ 2026-07-19 10:36:50
●NSns1.gcorelabs.net2026-07-19 → 2026-07-19 · 3 obs
● 2026-07-19 10:36:48
● 2026-07-19 10:36:50
○NSns2.digitalocean.com2017-12-13 → 2021-09-26 · 5 obs
● 2017-12-13 06:42:30
● 2021-09-26 12:18:30
○ 2026-07-19 10:36:48
○ 2026-07-19 10:36:50
●NSns2.gcdn.services2026-07-19 → 2026-07-19 · 3 obs
● 2026-07-19 10:36:48
● 2026-07-19 10:36:50
○NSns3.digitalocean.com2017-12-13 → 2021-09-26 · 5 obs
● 2017-12-13 06:42:30
● 2021-09-26 12:18:30
○ 2026-07-19 10:36:48
○ 2026-07-19 10:36:50
●MXalt1.aspmx.l.google.com2017-12-13 → 2026-07-19 · 3 obs
● 2017-12-13 06:42:30
● 2026-07-19 10:36:50
●MXalt2.aspmx.l.google.com2017-12-13 → 2026-07-19 · 3 obs
● 2017-12-13 06:42:30
● 2026-07-19 10:36:50
●MXalt3.aspmx.l.google.com2017-12-13 → 2026-07-19 · 3 obs
● 2017-12-13 06:42:30
● 2026-07-19 10:36:50
●MXalt4.aspmx.l.google.com2017-12-13 → 2026-07-19 · 3 obs
● 2017-12-13 06:42:30
● 2026-07-19 10:36:50
●MXaspmx.l.google.com2017-12-13 → 2026-07-19 · 3 obs
● 2017-12-13 06:42:30
● 2026-07-19 10:36:50
○MXmx.yandex.ru2016-12-05 → 2017-02-17 · 4 obs
● 2017-02-17 07:26:08
○ 2017-12-13 06:42:30
○ 2026-07-19 10:36:50
○A128.199.46.232017-02-17 → 2017-12-13 · 5 obs
● 2017-02-17 07:26:08
● 2017-12-13 06:42:30
○ 2021-05-23 07:20:48
○ 2026-07-19 10:36:50
○A165.22.91.2192026-02-16 → 2026-02-27 · 5 obs
● 2026-02-16 07:20:42
● 2026-02-27 03:30:46
○ 2026-03-30 01:50:52
○ 2026-07-19 10:36:50
○A176.123.182.972026-06-18 → 2026-06-18 · 4 obs
● 2026-06-18 09:16:42
○ 2026-07-19 10:36:48
○ 2026-07-19 10:36:50
○A188.165.154.212016-12-05 → 2016-12-05 · 3 obs
○ 2017-02-17 07:26:08
○ 2026-07-19 10:36:50
○A37.151.92.2102026-03-30 → 2026-06-07 · 5 obs
● 2026-03-30 01:50:52
● 2026-06-07 04:22:56
○ 2026-06-18 09:16:42
○ 2026-07-19 10:36:50
●A45.82.31.2472026-07-19 → 2026-07-19 · 3 obs
● 2026-07-19 10:36:48
● 2026-07-19 10:36:50
○A46.101.169.752021-05-23 → 2021-09-26 · 5 obs
● 2021-05-23 07:20:48
● 2021-09-26 12:18:30
○ 2026-02-16 07:20:42
○ 2026-07-19 10:36:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net... | - |
| forklog.com | ns1.gcorelabs.net, ns2.gcdn.services | - |
✅ Authoritative Response
Server:92.223.100.253
NS records: ns1.gcorelabs.net, ns2.gcdn.services
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for forklog.com (unsigned zone)
⏱️ Timing
Total: 288ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.82.31.247 |
| NS | 2 | ns2.gcdn.services, ns1.gcorelabs.net |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 include:_spf.google.com include:s, google-site-verification=vi-VoOjGnzGcLzC |
| SOA | 1 | ns1.gcorelabs.net support.gcore.com |
Analysis
IP Addresses
forklog.com resolves to just one IP address, 45.82.31.247.
Name Servers
forklog.com has two authoritative name servers — ns1.gcorelabs.net and ns2.gcdn.services.
forklog.com shares its NS records with other domains, for example apparelgallerybd.com, wxxw.de, myrl.net and two others.
forklog.com shares at least some of its name servers with other domains, including profoto.photography, hanusia.eu, ubezpieczeniagarwolin.pl and two others.
These name servers are frequently seen alongside the name servers ns1.webwavecms.com, ns2.webwavecms.com, ns1.webwave.me and ns2.webwave.me.
ns1.gcorelabs.net and ns2.gcdn.services each resolve to three IP addresses. ns1.gcorelabs.net resolves to 92.223.100.53, 92.223.100.253 and 2a03:90c0:9990::1053. ns2.gcdn.services resolves to 92.223.77.53, 92.223.77.253 and 2a03:90c0:9990::2053.
Mail Servers
forklog.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between forklog.com and other domains, including eali.com.br, ns500734.ns500693.ns500734.ns500734.ns500734.ns500699.ns500728.ns500693.ns500699.ns500588.ns500588.ns500683.ns500632.dtrkdll.com, ns500768.ns500758.ns500759.ns500759.ns500759.ns500735.ns500698.ns500698.ns500736.ns500698.ns500576.ns500686.ns500619.trackreceptor.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com resolves to 192.178.155.26 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.