aggressive-forces.com - robtex.com
aggressive-forces.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.verifymywhois.com ⚠️ Not in zone NS records | ||||||
| A | 209.235.147.130🇨🇦 INFB209.235.144.0/20 619A Kumpf Drive Waterloo ON N2V 1K8 Canada | ||||||
| PTR | ns1.verifymywhois.com | ||||||
| NS | ns2.verifymywhois.com ⚠️ Not in zone NS records | ||||||
| A | 209.235.147.131🇨🇦 INFB209.235.144.0/20 619A Kumpf Drive Waterloo ON N2V 1K8 Canada | ||||||
| PTR | ns2.verifymywhois.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=1784450847 | ||||||
Same first word
aggressive-forces.com |
DNS History
10 records (2 active, 8 former)
○NS64.29.151.2092026-03-14 → 2026-03-14 · 4 obs
○ 2017-04-06 21:45:44
● 2026-03-14 14:28:52
○ 2026-07-08 14:09:32
○ 2026-07-19 09:06:00
● 2026-03-14 14:28:52
○ 2026-07-08 14:09:32
○ 2026-07-19 09:06:00
○NSns1.creeksidefarms.us2017-04-06 → 2017-04-06 · 3 obs
● 2017-04-06 21:45:44
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
○NSns1.nxed.com2017-04-06 → 2017-04-06 · 3 obs
● 2017-04-06 21:45:44
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
●NSns1.verifymywhois.com2026-03-14 → 2026-07-19 · 3 obs
○ 2017-04-06 21:45:44
● 2026-03-14 14:28:52
● 2026-07-19 09:06:00
● 2026-03-14 14:28:52
● 2026-07-19 09:06:00
○NSns2.creeksidefarms.us2017-04-06 → 2017-04-06 · 3 obs
● 2017-04-06 21:45:44
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
○NSns2.nxed.com2017-04-06 → 2017-04-06 · 3 obs
● 2017-04-06 21:45:44
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
●NSns2.verifymywhois.com2026-03-14 → 2026-07-19 · 3 obs
○ 2017-04-06 21:45:44
● 2026-03-14 14:28:52
● 2026-07-19 09:06:00
● 2026-03-14 14:28:52
● 2026-07-19 09:06:00
○NSns3.nxed.com2017-04-06 → 2017-04-06 · 3 obs
● 2017-04-06 21:45:44
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
○ 2026-03-14 14:28:52
○ 2026-07-19 09:06:00
○A64.29.151.2092026-03-14 → 2026-03-14 · 3 obs
● 2026-03-14 14:28:52
○ 2026-07-08 14:09:32
○ 2026-07-19 09:06:00
○ 2026-07-08 14:09:32
○ 2026-07-19 09:06:00
○CNAME64.29.151.2092026-03-14 → 2026-03-14 · 3 obs
● 2026-03-14 14:28:52
○ 2026-07-08 14:09:32
○ 2026-07-19 09:06:00
○ 2026-07-08 14:09:32
○ 2026-07-19 09:06:00
🔍 DNS Trace
Analysis
Name Servers
The NS records for aggressive-forces.com delegate to ns1.verifymywhois.com and ns2.verifymywhois.com.
aggressive-forces.com uses the same name servers as several other domains — among them betanest.com, amexpc.com, hsnrn.com and two more.
Both ns1.verifymywhois.com and ns2.verifymywhois.com have a single IP address each — ns1.verifymywhois.com resolves to 209.235.147.130 while ns2.verifymywhois.com resolves to 209.235.147.131.