howshouldidress.com - robtex.com
howshouldidress.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=1771291435 | ||||||
Same first word
howshouldidress.com |
DNS History
7 records (6 active, 1 former)
●NSns55.domaincontrol.com2015-08-19 → 2026-03-23 · 2 obs
● 2026-03-23 20:41:08
●NSns56.domaincontrol.com2015-08-19 → 2026-03-23 · 2 obs
● 2026-03-23 20:41:08
●MXmailstore1.secureserver.net2015-08-19 → 2026-03-23 · 2 obs
● 2026-03-23 20:41:08
●MXsmtp.secureserver.net2015-08-19 → 2026-03-23 · 2 obs
● 2026-03-23 20:41:08
●A15.197.148.332026-02-20 → 2026-03-23 · 3 obs
● 2026-02-20 22:30:30
● 2026-03-23 20:41:08
●A3.33.130.1902026-02-20 → 2026-03-23 · 3 obs
● 2026-02-20 22:30:30
● 2026-03-23 20:41:08
○A50.63.202.532015-08-19 → 2020-02-21 · 4 obs
● 2020-02-21 10:05:00
○ 2026-02-20 22:30:30
○ 2026-03-23 20:41:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| howshouldidress.com | ns55.domaincontrol.com, ns56.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.75.28
NS records: ns55.domaincontrol.com, ns56.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for howshouldidress.com (unsigned zone)
⏱️ Timing
Total: 96ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns55.domaincontrol.com, ns56.domaincontrol.com |
| MX | 2 | mailstore1.secureserver.net (pri: 10), smtp.secureserver.net (pri: 0) |
| SOA | 1 | ns55.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns55.domaincontrol.com, ns55.domaincontrol.com, ns56.domaincontrol.com...)
Analysis
IP Addresses
howshouldidress.com points to two IP numbers: 3.33.130.190 and 15.197.148.33.
Other host names, for instance eyeblazer.com, gotanica.com, mc2usa.com, nextgenandroid.com and urbinatti.com.mx share IP numbers with howshouldidress.com.
Name Servers
Delegation for howshouldidress.com rests with two name servers, ns55.domaincontrol.com and ns56.domaincontrol.com.
howshouldidress.com shares the same name server setup as other domains, including trustedoil.com, ictoo.com, stmginc.com, atlantic-equipment.com and kktrailersales.com.
Host names with two IP numbers: ns55.domaincontrol.com points to 2603:5:21b2::1c and 97.74.107.28; ns56.domaincontrol.com points to 2603:5:22b2::1c and 173.201.75.28.
Mail Servers
howshouldidress.com is handled by two mail servers: mailstore1.secureserver.net and smtp.secureserver.net.
howshouldidress.com uses the same mail server configuration as other domains, such as northsidemhc.org, therocksat.info, dsohub.net, m4me.biz and starfields.co.
howshouldidress.com shares at least partially some mail servers with other domains, for example codecollab.org, go4tickets.com and pyrexiacare.com.
Host names with three IP numbers: The host name mailstore1.secureserver.net points to 216.69.141.78, 216.69.141.114 and 216.69.141.162; The host name smtp.secureserver.net points to 216.69.141.71, 216.69.141.84 and 216.69.141.113.