boylecounty.com - robtex.com
boylecounty.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| 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 | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@boylecounty.com 2025-08-27 #2 | ||||||
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=1774498667 | ||||||
Same first word
boylecounty.com |
DNS History
18 records (3 active, 15 former)
○NSbuy.internettraffic.com2015-08-10 → 2015-08-10 · 4 obs
○ 2007-11-06 03:14:14
● 2015-08-10 00:11:34
○ 2015-12-15 22:17:12
○ 2026-03-26 04:48:14
● 2015-08-10 00:11:34
○ 2015-12-15 22:17:12
○ 2026-03-26 04:48:14
○NSgeo1.spectacular.com2015-12-15 → 2017-03-18 · 5 obs
○ 2015-08-10 00:11:34
● 2015-12-15 22:17:12
● 2017-03-18 13:54:00
○ 2020-01-21 18:09:48
○ 2026-03-26 04:48:14
● 2015-12-15 22:17:12
● 2017-03-18 13:54:00
○ 2020-01-21 18:09:48
○ 2026-03-26 04:48:14
○NSgeo2.spectacular.com2015-12-15 → 2017-03-18 · 5 obs
○ 2015-08-10 00:11:34
● 2015-12-15 22:17:12
● 2017-03-18 13:54:00
○ 2020-01-21 18:09:48
○ 2026-03-26 04:48:14
● 2015-12-15 22:17:12
● 2017-03-18 13:54:00
○ 2020-01-21 18:09:48
○ 2026-03-26 04:48:14
●NSns1.atom.com2026-02-17 → 2026-03-26 · 3 obs
○ 2020-01-21 18:09:48
● 2026-02-17 15:21:22
● 2026-03-26 04:48:14
● 2026-02-17 15:21:22
● 2026-03-26 04:48:14
○NSns1.uniregistrymarket.link2020-01-21 → 2020-01-21 · 4 obs
○ 2017-03-18 13:54:00
● 2020-01-21 18:09:48
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
● 2020-01-21 18:09:48
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
●NSns2.atom.com2026-02-17 → 2026-03-26 · 3 obs
○ 2020-01-21 18:09:48
● 2026-02-17 15:21:22
● 2026-03-26 04:48:14
● 2026-02-17 15:21:22
● 2026-03-26 04:48:14
○NSns2.uniregistrymarket.link2020-01-21 → 2020-01-21 · 4 obs
○ 2017-03-18 13:54:00
● 2020-01-21 18:09:48
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
● 2020-01-21 18:09:48
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
○NSns8.citiesunlimited.com2007-11-06 → 2007-11-06 · 3 obs
● 2007-11-06 03:14:14
○ 2015-08-10 00:11:34
○ 2026-03-26 04:48:14
○ 2015-08-10 00:11:34
○ 2026-03-26 04:48:14
○NSns9.citiesunlimited.com2007-11-06 → 2007-11-06 · 3 obs
● 2007-11-06 03:14:14
○ 2015-08-10 00:11:34
○ 2026-03-26 04:48:14
○ 2015-08-10 00:11:34
○ 2026-03-26 04:48:14
○NSsell.internettraffic.com2015-08-10 → 2015-08-10 · 4 obs
○ 2007-11-06 03:14:14
● 2015-08-10 00:11:34
○ 2015-12-15 22:17:12
○ 2026-03-26 04:48:14
● 2015-08-10 00:11:34
○ 2015-12-15 22:17:12
○ 2026-03-26 04:48:14
○MXmx247.in-mx.com2020-01-21 → 2020-01-21 · 3 obs
● 2020-01-21 18:09:48
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
○MXmx247.in-mx.net2020-01-21 → 2020-01-21 · 3 obs
● 2020-01-21 18:09:48
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
○A139.146.143.52007-11-06 → 2007-11-06 · 3 obs
● 2007-11-06 03:14:14
○ 2015-08-10 00:11:34
○ 2026-03-26 04:48:14
○ 2015-08-10 00:11:34
○ 2026-03-26 04:48:14
○A139.146.144.52007-11-06 → 2007-11-06 · 3 obs
● 2007-11-06 03:14:14
○ 2015-08-10 00:11:34
○ 2026-03-26 04:48:14
○ 2015-08-10 00:11:34
○ 2026-03-26 04:48:14
○A192.81.170.2202015-12-15 → 2017-03-18 · 5 obs
○ 2015-08-10 00:11:34
● 2015-12-15 22:17:12
● 2017-03-18 13:54:00
○ 2020-01-21 18:09:48
○ 2026-03-26 04:48:14
● 2015-12-15 22:17:12
● 2017-03-18 13:54:00
○ 2020-01-21 18:09:48
○ 2026-03-26 04:48:14
●A52.20.84.622026-02-17 → 2026-03-26 · 3 obs
○ 2020-01-21 18:09:48
● 2026-02-17 15:21:22
● 2026-03-26 04:48:14
● 2026-02-17 15:21:22
● 2026-03-26 04:48:14
○A69.172.201.1532020-01-21 → 2020-01-21 · 4 obs
○ 2017-03-18 13:54:00
● 2020-01-21 18:09:48
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
● 2020-01-21 18:09:48
○ 2026-02-17 15:21:22
○ 2026-03-26 04:48:14
○A69.172.201.2082015-08-10 → 2015-08-10 · 4 obs
○ 2007-11-06 03:14:14
● 2015-08-10 00:11:34
○ 2015-12-15 22:17:12
○ 2026-03-26 04:48:14
● 2015-08-10 00:11:34
○ 2015-12-15 22:17:12
○ 2026-03-26 04:48:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| boylecounty.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for boylecounty.com (unsigned zone)
⏱️ Timing
Total: 3114ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.boylecounty.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
boylecounty.com points to a single IP: 52.20.84.62.
Other host names, for instance vwal.com, electricsonic.com, skyemr.com, ibtn.com and couplenest.com share IP numbers with boylecounty.com.
Name Servers
boylecounty.com's delegation is to two name servers ns1.atom.com and ns2.atom.com.
boylecounty.com shares the same name server configuration as other domains, such as biopard.com, appavid.com, westmiami.com, albula.com and eureum.com.
Host names with a single IP:
ns1.atom.com resolves to 44.219.81.145.
ns2.atom.com resolves to 50.19.240.86.