pepgear.com - dns.ninja
pepgear.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 | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| SOA | ns1.atom.comhostmaster@pepgear.com 2026-03-30 #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=1783084861 | ||||||
Same first word
pepgear.com |
Similar names
DNS History
12 records (3 active, 9 former)
○NSno-dyn-updates.san.yahoo.com2015-06-06 → 2017-08-08 · 4 obs
● 2017-08-08 00:35:18
○ 2026-03-26 01:53:32
○ 2026-07-03 13:28:30
●NSns1.atom.com2026-04-13 → 2026-07-03 · 3 obs
● 2026-04-13 16:37:46
● 2026-07-03 13:28:30
●NSns2.atom.com2026-04-13 → 2026-07-03 · 3 obs
● 2026-04-13 16:37:46
● 2026-07-03 13:28:30
○NSns5.afternic.com2026-03-26 → 2026-03-26 · 4 obs
● 2026-03-26 01:53:32
○ 2026-04-13 16:37:46
○ 2026-07-03 13:28:30
○NSns6.afternic.com2026-03-26 → 2026-03-26 · 4 obs
● 2026-03-26 01:53:32
○ 2026-04-13 16:37:46
○ 2026-07-03 13:28:30
○NSyns1.yahoo.com2015-06-06 → 2017-08-08 · 4 obs
● 2017-08-08 00:35:18
○ 2026-03-26 01:53:32
○ 2026-07-03 13:28:30
○NSyns2.yahoo.com2015-06-06 → 2017-08-08 · 4 obs
● 2017-08-08 00:35:18
○ 2026-03-26 01:53:32
○ 2026-07-03 13:28:30
○MXmx1.wss.scd.yahoo.com2015-06-06 → 2017-08-08 · 4 obs
● 2017-08-08 00:35:18
○ 2026-03-26 01:53:32
○ 2026-07-03 13:28:30
○A13.248.169.482026-03-26 → 2026-03-26 · 4 obs
● 2026-03-26 01:53:32
○ 2026-04-13 16:37:46
○ 2026-07-03 13:28:30
●A52.20.84.622026-04-13 → 2026-07-03 · 3 obs
● 2026-04-13 16:37:46
● 2026-07-03 13:28:30
○A66.218.85.1692015-06-06 → 2017-08-08 · 4 obs
● 2017-08-08 00:35:18
○ 2026-03-26 01:53:32
○ 2026-07-03 13:28:30
○A76.223.54.1462026-03-26 → 2026-03-26 · 4 obs
● 2026-03-26 01:53:32
○ 2026-04-13 16:37:46
○ 2026-07-03 13:28:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| pepgear.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 pepgear.com (unsigned zone)
⏱️ Timing
Total: 3765ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| TXT | 1 | f0095018235b8109a2bf9f65674a1784b6971ed6 |
| SOA | 1 | ns1.atom.com hostmaster.pepgear.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
pepgear.com resolves to one IP address: 52.20.84.62.
ownvox.com, stand.yachts, birdradio.com and two other host names share IP numbers with pepgear.com.
Name Servers
pepgear.com is served by two delegated name servers, ns1.atom.com and ns2.atom.com.
pepgear.com uses the same name servers as several other domains — among them groovejuice.com, kiffu.com, leonel.us and two more.
pepgear.com has at least partial name server overlap with other domains, such as yy8.net, blogspot.lol, ibqk.com and two others.
It is common to find these name servers paired with the name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn.
ns1.atom.com directs to 44.219.81.145 and ns2.atom.com directs to 50.19.240.86; each host name points to exactly one IP number.