forgingfire.com - dns.ninja

forgingfire.com

DNSSEC⚠️ Not signed
A52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix
PTRec2-52-20-84-62.compute-1.amazonaws.com
NSns1.squadhelp.com ⭐
A52.201.79.206🇺🇸 Amazon52.200.0.0/13 EC2 IAD prefix
PTRec2-52-201-79-206.compute-1.amazonaws.com
NSns2.squadhelp.com
A52.23.148.124🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix
PTRec2-52-23-148-124.compute-1.amazonaws.com
TXTf0095018235b8109a2bf9f65674a1784b6971ed6
SOAns1.squadhelp.comhostmaster@forgingfire.com 2025-10-25 #1

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1785902464

Same first word

forgingfire.com

DNS History

8 records (3 active, 5 former)

20162017201820192020202120222023202420252026NSns1.squadhelp.comns2.squadhelp.comsk.s5.ans1.ns117.ztomy.comsk.s5.ans2.ns117.ztomy.comA52.20.84.62141.8.224.124208.91.196.74PTRsk.s5.ans1.ns117.ztomy.com
●NSns1.squadhelp.com2026-05-27 → 2026-08-05 · 3 obs
○ 2019-03-03 02:16:54
● 2026-05-27 14:26:42
● 2026-08-05 04:18:00
●NSns2.squadhelp.com2026-05-27 → 2026-08-05 · 3 obs
○ 2019-03-03 02:16:54
● 2026-05-27 14:26:42
● 2026-08-05 04:18:00
○NSsk.s5.ans1.ns117.ztomy.com2015-07-11 → 2019-03-03 · 4 obs
● 2015-07-11 10:31:46
● 2019-03-03 02:16:54
○ 2026-05-27 14:26:42
○ 2026-08-05 04:18:00
○NSsk.s5.ans2.ns117.ztomy.com2015-07-11 → 2019-03-03 · 4 obs
● 2015-07-11 10:31:46
● 2019-03-03 02:16:54
○ 2026-05-27 14:26:42
○ 2026-08-05 04:18:00
○A141.8.224.1242015-07-11 → 2017-02-10 · 4 obs
● 2015-07-11 10:31:46
● 2017-02-10 03:36:14
○ 2019-03-03 02:16:54
○ 2026-08-05 04:18:00
○A208.91.196.742019-03-03 → 2019-03-03 · 4 obs
○ 2017-02-10 03:36:14
● 2019-03-03 02:16:54
○ 2026-05-27 14:26:42
○ 2026-08-05 04:18:00
●A52.20.84.622026-05-27 → 2026-08-05 · 3 obs
○ 2019-03-03 02:16:54
● 2026-05-27 14:26:42
● 2026-08-05 04:18:00
○PTRsk.s5.ans1.ns117.ztomy.com2017-02-10 → 2019-03-03 · 4 obs
● 2017-02-10 03:36:14
● 2019-03-03 02:16:54
○ 2026-05-27 14:26:42
○ 2026-08-05 04:18:00

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...-
forgingfire.comns1.squadhelp.com, ns2.squadhelp.com2 records

✅ Authoritative Response

Server:52.201.79.206

NS records: ns1.squadhelp.com, ns2.squadhelp.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for forgingfire.com (unsigned zone)

⏱️ Timing

Total: 107ms | Queries: -

📄 Records

TypeCountSample Data
A152.20.84.62
NS2ns1.squadhelp.com, ns2.squadhelp.com
TXT1f0095018235b8109a2bf9f65674a1784b6971ed6
SOA1ns1.squadhelp.com hostmaster.forgingfire

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.squadhelp.com, ns2.squadhelp.com)

Analysis

IP Addresses

forgingfire.com resolves to one IP address: 52.20.84.62.

shosk.com, forumchina.com, nuvlo.com and two other host names share IP numbers with forgingfire.com.

Name Servers

Two name servers handle the delegation for forgingfire.com: ns1.squadhelp.com and ns2.squadhelp.com.

forgingfire.com uses the same name servers as several other domains — among them dolavo.com, (0x736578)ydreams.com, rapidific.com and two more.

The name servers for forgingfire.com are partially shared with other domains like voidxr.com, revodo.com and capitalhappy.com

ns1.squadhelp.com resolves to 52.201.79.206. ns2.squadhelp.com resolves to 52.23.148.124. Both host names point to a single IP number.