smsize.com - dns.ninja
smsize.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=1785931224 | ||||||
Same first word
smsize.com |
Similar names
DNS History
10 records (5 active, 5 former)
●NSdns1.registrar-servers.com2026-07-09 → 2026-08-05 · 3 obs
● 2026-07-09 13:52:52
● 2026-08-05 12:08:30
●NSdns2.registrar-servers.com2026-07-09 → 2026-08-05 · 3 obs
● 2026-07-09 13:52:52
● 2026-08-05 12:08:30
○NSns21.domaincontrol.com2015-06-05 → 2018-09-13 · 4 obs
● 2018-09-13 06:32:20
○ 2026-04-08 18:41:22
○ 2026-08-05 12:08:30
○NSns22.domaincontrol.com2015-06-05 → 2018-09-13 · 4 obs
● 2018-09-13 06:32:20
○ 2026-04-08 18:41:22
○ 2026-08-05 12:08:30
○MXmailzm.smsize.com2015-06-05 → 2017-02-02 · 4 obs
● 2017-02-02 14:57:02
○ 2018-09-13 06:32:20
○ 2026-08-05 12:08:30
●MXmx1.privateemail.com2026-07-09 → 2026-08-05 · 3 obs
● 2026-07-09 13:52:52
● 2026-08-05 12:08:30
●MXmx2.privateemail.com2026-07-09 → 2026-08-05 · 3 obs
● 2026-07-09 13:52:52
● 2026-08-05 12:08:30
○A50.62.72.1602015-06-05 → 2017-02-02 · 4 obs
● 2017-02-02 14:57:02
○ 2018-09-13 06:32:20
○ 2026-08-05 12:08:30
●A66.29.146.1922026-07-09 → 2026-08-05 · 3 obs
● 2026-07-09 13:52:52
● 2026-08-05 12:08:30
○A97.74.125.2342018-09-13 → 2018-09-13 · 4 obs
● 2018-09-13 06:32:20
○ 2026-04-08 18:41:22
○ 2026-08-05 12:08:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net... | - |
| smsize.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for smsize.com (unsigned zone)
⏱️ Timing
Total: 132ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.29.146.192 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 2 | mx1.privateemail.com (pri: 10), mx2.privateemail.com (pri: 10) |
| TXT | 1 | v=spf1 include:spf.privateemail.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
smsize.com resolves to just one IP address, 66.29.146.192.
Two other host names, along with mail.tom-bennett.co, mail.frozenfoodsupplies.com and alertv.com, also share IP numbers with smsize.com.
Name Servers
smsize.com uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
smsize.com shares its NS records with other domains, for example furixturi.com, happense.com, pgpkecpebayuran.org and two others.
smsize.com partially shares its NS delegation with several other domains, including coinfest.co, radmill.com, distilledodn.net and two others.
These name servers regularly co-occur 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
smsize.com is served by two mail servers, mx1.privateemail.com and mx2.privateemail.com.
Among the domains sharing a mail server setup with smsize.com are xfrdata.com, traclytics.com, intermil.org and two others.
smsize.com partially shares its mail servers with other domains, alrconsultoria.com and sideload.me being examples.
mx1.privateemail.com resolves to 162.255.118.7. mx2.privateemail.com resolves to 162.255.118.8. Both host names point to a single IP number.