robotobor.com - robtex.com
robotobor.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=1774633287 | ||||||
MX for
robotobor.com |
Same first word
robotobor.com |
robotobor.pro |
Similar names
DNS History
8 records (6 active, 2 former)
●NSns0.transip.net2019-12-28 → 2026-03-27 · 3 obs
● 2019-12-28 12:23:48
● 2026-03-27 18:05:02
○NSns0.transip.nl2015-08-07 → 2017-02-17 · 5 obs
● 2015-08-07 19:26:50
● 2017-02-17 12:41:58
○ 2019-12-28 12:23:48
○ 2026-03-27 18:05:02
●NSns1.transip.nl2015-08-07 → 2026-03-27 · 3 obs
● 2015-08-07 19:26:50
● 2026-03-27 18:05:02
●NSns2.transip.eu2019-12-28 → 2026-03-27 · 3 obs
● 2019-12-28 12:23:48
● 2026-03-27 18:05:02
○NSns2.transip.nl2015-08-07 → 2017-02-17 · 5 obs
● 2015-08-07 19:26:50
● 2017-02-17 12:41:58
○ 2019-12-28 12:23:48
○ 2026-03-27 18:05:02
●MXrelay.transip.nl2015-08-07 → 2026-03-27 · 3 obs
● 2015-08-07 19:26:50
● 2026-03-27 18:05:02
●MXrobotobor.com2015-08-07 → 2026-03-27 · 3 obs
● 2015-08-07 19:26:50
● 2026-03-27 18:05:02
●A84.41.166.2042008-03-17 → 2026-03-27 · 2 obs
● 2026-03-27 18:05:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, b.gtld-servers.net, j.gtld-servers.net, d.gtld-servers.net... | - |
| robotobor.com | ns1.transip.nl, ns0.transip.net, ns2.transip.eu | - |
✅ Authoritative Response
Server:195.8.195.195
NS records: ns1.transip.nl, ns0.transip.net, ns2.transip.eu
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 435ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 84.41.166.204 |
| NS | 3 | ns0.transip.net, ns2.transip.eu... |
| MX | 2 | relay.transip.nl (pri: 20), robotobor.com (pri: 10) |
| SOA | 1 | ns0.transip.net hostmaster.transip.nl |
Analysis
Mail Server Role
robotobor.com serves as the mail server for robotobor.com.
relay.transip.nl is commonly used as a mail server alongside robotobor.com.
IP Addresses
robotobor.com resolves to one IP number: 84.41.166.204.
Name Servers
robotobor.com is delegated to three name servers: ns2.transip.eu, ns0.transip.net and ns1.transip.nl.
robotobor.com at least partially shares name servers with other domains, including syntegro.be, pdp.me, ministryofpinball.de, jzhl.nl and xperiencentral.eu.
Host names with two IP numbers:
ns2.transip.eu: 2a01:7c8:f:c1f::195 and 37.97.199.195
ns0.transip.net: 2a01:7c8:dddd:195::195 and 195.135.195.195
ns1.transip.nl: 2a01:7c8:7000:195::195 and 195.8.195.195
Mail Servers
robotobor.com is handled by two mail servers: robotobor.com and relay.transip.nl.
robotobor.com shares at least some mail servers with other domains, for example originalsneaker.nl, pl-ventures.nl, ysolde.eu, linos.nl and ydroj.nl.
These mail servers are commonly used with mail.diningcity.com, aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with four IP numbers: relay.transip.nl points to 2a01:7c8:7c8::12, 2a01:7c8:7c8::29, 149.210.149.12 and 149.210.149.29.
Host names with one IP number: robotobor.com points to 84.41.166.204.