firstregiment.com - dns.ninja
firstregiment.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.atom.com ⚠️ Not in zone NS records | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com ⚠️ Not in zone NS records | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| NS | verification-nleonmcfkcimdoyulhuayj.ns101.verify.hn ⚠️ Not in zone NS records | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.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=1782104585 | ||||||
Previously MX for
firstregiment.com |
Same first word
firstregiment.com |
DNS History
8 records (3 active, 5 former)
●NSns1.atom.com2026-02-17 → 2026-06-22 · 3 obs
○ 2017-04-05 07:44:00
● 2026-02-17 12:23:50
● 2026-06-22 05:17:08
● 2026-02-17 12:23:50
● 2026-06-22 05:17:08
○NSns1.ideaserved.com2015-07-10 → 2017-04-05 · 4 obs
● 2015-07-10 07:43:18
● 2017-04-05 07:44:00
○ 2026-02-17 12:23:50
○ 2026-06-22 05:17:08
● 2017-04-05 07:44:00
○ 2026-02-17 12:23:50
○ 2026-06-22 05:17:08
●NSns2.atom.com2026-02-17 → 2026-06-22 · 3 obs
○ 2017-04-05 07:44:00
● 2026-02-17 12:23:50
● 2026-06-22 05:17:08
● 2026-02-17 12:23:50
● 2026-06-22 05:17:08
○NSns2.ideaserved.com2015-07-10 → 2017-04-05 · 4 obs
● 2015-07-10 07:43:18
● 2017-04-05 07:44:00
○ 2026-02-17 12:23:50
○ 2026-06-22 05:17:08
● 2017-04-05 07:44:00
○ 2026-02-17 12:23:50
○ 2026-06-22 05:17:08
●NSverification-nleonmcfkcimdoyulhuayj.ns101.verify.hn2026-02-17 → 2026-06-22 · 3 obs
○ 2017-04-05 07:44:00
● 2026-02-17 12:23:50
● 2026-06-22 05:17:08
● 2026-02-17 12:23:50
● 2026-06-22 05:17:08
○MXfirstregiment.com2015-07-10 → 2017-04-05 · 4 obs
● 2015-07-10 07:43:18
● 2017-04-05 07:44:00
○ 2026-02-17 12:23:50
○ 2026-06-22 05:17:08
● 2017-04-05 07:44:00
○ 2026-02-17 12:23:50
○ 2026-06-22 05:17:08
○A52.20.84.622026-02-17 → 2026-05-23 · 5 obs
○ 2017-04-05 07:44:00
● 2026-02-17 12:23:50
● 2026-05-23 00:28:06
○ 2026-06-22 05:17:06
○ 2026-06-22 05:17:08
● 2026-02-17 12:23:50
● 2026-05-23 00:28:06
○ 2026-06-22 05:17:06
○ 2026-06-22 05:17:08
○A69.73.181.1302015-07-10 → 2017-04-05 · 4 obs
● 2015-07-10 07:43:18
● 2017-04-05 07:44:00
○ 2026-02-17 12:23:50
○ 2026-06-22 05:17:08
● 2017-04-05 07:44:00
○ 2026-02-17 12:23:50
○ 2026-06-22 05:17:08
🔍 DNS Trace
Analysis
Name Servers
firstregiment.com carries NS records delegating to ns1.atom.com, ns2.atom.com and verification-nleonmcfkcimdoyulhuayj.ns101.verify.hn.
At least some of firstregiment.com's name servers are shared with other domains, for example sarfit.com, bizgt.com, andbewell.com and two more.
These name servers tend to be used in conjunction with the name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn.
Host names pointing to two IP addresses:
verification-nleonmcfkcimdoyulhuayj.ns101.verify.hn resolves to two addresses: 13.248.169.48 and 76.223.54.146.
Host names resolving to a single IP address:
The hostname ns1.atom.com resolves to 44.219.81.145.
The hostname ns2.atom.com resolves to 50.19.240.86.