rubyforpm.com - dns.ninja
rubyforpm.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=1790517944 | ||||||
Same first word
Previous names
Next names
rubyforrails.com |
rubyforsystemadministrators.com |
rubyfort.com |
rubyfortine.com |
rubyfortube.com |
rubyfortun.com |
rubyfortune-ca.com |
rubyfortune-canada.com |
rubyfortune-casino-ca.com |
rubyfortune.com |
DNS History
9 records (9 active, 0 former)
●NSns41.domaincontrol.com2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 14:10:50
●NSns42.domaincontrol.com2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 14:10:50
●MXalt1.aspmx.l.google.com2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 14:10:50
●MXalt2.aspmx.l.google.com2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 14:10:50
●MXalt3.aspmx.l.google.com2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 14:10:50
●MXalt4.aspmx.l.google.com2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 14:10:50
●MXaspmx.l.google.com2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 14:10:50
●A15.197.225.1282026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 14:10:50
●A3.33.251.1682026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 14:10:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net, l.gtld-servers.net... | - |
| rubyforpm.com | ns41.domaincontrol.com, ns42.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.100.21
NS records: ns41.domaincontrol.com, ns42.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rubyforpm.com (unsigned zone)
⏱️ Timing
Total: 213ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns42.domaincontrol.com, ns41.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=KyRktzke57mv2ya, v=spf1 include:dc-aa8e722993._spfm.rubyf |
| SOA | 1 | ns41.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns41.domaincontrol.com, ns41.domaincontrol.com, ns42.domaincontrol.com...)
Analysis
IP Addresses
rubyforpm.com directs to two IP numbers, 3.33.251.168 and 15.197.225.128
explorehocking.org, kohlerscycle.com, digitalgalley.net plus two other host names have IP numbers in common with rubyforpm.com.
Name Servers
rubyforpm.com uses two name servers for its delegation: ns41.domaincontrol.com and ns42.domaincontrol.com.
The name server configuration of rubyforpm.com is shared with other domains, for instance mementomori.ca, filigranaholding.com, vailiceguides.com and two others.
At least some of rubyforpm.com's name servers are also used by other domains, among them smartnews-smri.com.
The two host names ns41.domaincontrol.com and ns42.domaincontrol.com each have a pair of IP addresses: ns41.domaincontrol.com has 97.74.100.21 and 2603:5:2142::15, and ns42.domaincontrol.com has 173.201.68.21 and 2603:5:2242::15.
Mail Servers
Mail for rubyforpm.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by rubyforpm.com are shared with other domains: healthandbalance.net, vietactivegroup.com, camdenre.com and two others among them.
These mail servers often appear in conjunction with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx3.googlemail.com and aspmx2.googlemail.com.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 173.194.45.27 and 2607:f8b0:4004:c29::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.