opsmen.com - dns.ninja
opsmen.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=1786401544 | ||||||
PTR for
Same first word
opsmen.com |
Similar names
DNS History
9 records (8 active, 1 former)
●NSdns1.registrar-servers.com2016-12-05 → 2026-08-10 · 2 obs
● 2026-08-10 22:53:40
●NSdns2.registrar-servers.com2016-12-05 → 2026-08-10 · 2 obs
● 2026-08-10 22:53:40
●MXalt1.aspmx.l.google.com2016-12-05 → 2026-08-10 · 2 obs
● 2026-08-10 22:53:40
●MXalt2.aspmx.l.google.com2016-12-05 → 2026-08-10 · 2 obs
● 2026-08-10 22:53:40
●MXalt3.aspmx.l.google.com2016-12-05 → 2026-08-10 · 2 obs
● 2026-08-10 22:53:40
●MXalt4.aspmx.l.google.com2016-12-05 → 2026-08-10 · 2 obs
● 2026-08-10 22:53:40
●MXaspmx.l.google.com2016-12-05 → 2026-08-10 · 2 obs
● 2026-08-10 22:53:40
○A204.93.163.152016-12-05 → 2016-12-05 · 3 obs
○ 2018-06-01 17:11:56
○ 2026-08-10 22:53:40
●A23.239.22.652018-06-01 → 2026-08-10 · 3 obs
● 2018-06-01 17:11:56
● 2026-08-10 22:53:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, f.gtld-servers.net, c.gtld-servers.net, e.gtld-servers.net... | - |
| opsmen.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for opsmen.com (unsigned zone)
⏱️ Timing
Total: 476ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.239.22.65 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
IP Addresses
opsmen.com directs to one IP number, which is 23.239.22.65.
Name Servers
opsmen.com uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
opsmen.com has the same name server delegation as a number of other domains, such as trafficbingo.com, 21cir.com, adornhotels.com and two more.
There is an overlap in name servers between opsmen.com and other domains, for example ndabot.com, seswa.me and cashforthe.website
It is common for these name servers to be used in conjunction with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
Five mail servers handle opsmen.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
opsmen.com shares at least some of its mail servers with other domains — for example davanam.com, ns500731.ns500754.ns500742.ns500731.ns500731.ns500731.ns500742.ns500731.ns500742.ns500688.ns500688.ns500678.ns500291.ns500666.ns500291.ns500291.ns500131.lustychickser.com, ns500759.ns500758.ns500736.ns500736.ns500735.ns500735.ns500735.ns500736.ns500735.ns500708.ns500698.ns500708.ns500698.ns500619.ns500619.ns500619.trackreceptor.com and two more.
It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c07::1b.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.