royaldating.nl - robtex.com
royaldating.nl
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2600:9000:a612:55d9:577:681:d7ab:f42b🇺🇸 Amazon2600:9000:a600::/43 | ||||||
| PTR | a9bb9d6c6ba17ec4b.dualstack.awsglobalaccelerator.com | ||||||
| A | 3.33.236.10🇺🇸 Amazon3.33.224.0/20 | ||||||
| NS | ns1.dnsmanager.nl ⭐ | ||||||
| A | 2a01:a680:a1:f::155🇳🇱 VXbits2a01:a680::/32 | ||||||
| A | 141.138.151.155🇳🇱 VXbits141.138.144.0/21 | ||||||
| PTR | serv5.mooieserver.nl | ||||||
| NS | ns2.dnsmanager.nl | ||||||
| A | 2a01:a680:a1:f::156🇳🇱 VXbits2a01:a680::/32 | ||||||
| A | 141.138.151.156🇳🇱 VXbits141.138.144.0/21 | ||||||
| TXT | larzpb.rediredge.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.dnsmanager.nlhm@mediavillage.nl 2022-10-11 #0 | ||||||
nl
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns1.dns.nl ⭐ | ||||||
| NS | ns3.dns.nl | ||||||
| NS | ns4.dns.nl | ||||||
| TXT | nl zone update: 2026-05-13 08:30:01 +0000 (EPOCH 1778661001) | ||||||
| SOA | ns1.dns.nldns@sidn.nl 2026-05-13 #17 | ||||||
Subdomains
mx.royaldating.nl |
Same first word
royaldating.com |
royaldating.nl |
Similar names
DNS History
10 records (4 active, 6 former)
●NSns1.dnsmanager.nl2026-04-26 → 2026-05-13 · 3 obs
● 2026-04-26 17:22:20
● 2026-05-13 09:24:30
●NSns2.dnsmanager.nl2026-04-26 → 2026-05-13 · 3 obs
● 2026-04-26 17:22:20
● 2026-05-13 09:24:30
○NSnsauth1.bit.nl2015-07-06 → 2017-07-10 · 4 obs
● 2017-07-10 04:19:54
○ 2026-04-26 17:22:20
○ 2026-05-13 09:24:30
○NSnsauth2.bit.nl2015-07-06 → 2017-07-10 · 4 obs
● 2017-07-10 04:19:54
○ 2026-04-26 17:22:20
○ 2026-05-13 09:24:30
○NSnsauth3.bit.org2015-07-06 → 2017-07-10 · 4 obs
● 2017-07-10 04:19:54
○ 2026-04-26 17:22:20
○ 2026-05-13 09:24:30
○MXmx.royaldating.nl2015-07-06 → 2017-07-10 · 4 obs
● 2017-07-10 04:19:54
○ 2026-04-26 17:22:20
○ 2026-05-13 09:24:30
○A2001:7b8:3:5::80:12015-07-06 → 2017-07-10 · 4 obs
● 2017-07-10 04:19:54
○ 2026-04-26 17:22:20
○ 2026-05-13 09:24:30
○A213.136.12.2322015-07-06 → 2017-07-10 · 4 obs
● 2017-07-10 04:19:54
○ 2026-04-26 17:22:20
○ 2026-05-13 09:24:30
●A2600:9000:a612:55d9:577:681:d7ab:f42b2026-04-26 → 2026-05-13 · 3 obs
● 2026-04-26 17:22:20
● 2026-05-13 09:24:30
●A3.33.236.102026-04-26 → 2026-05-13 · 3 obs
● 2026-04-26 17:22:20
● 2026-05-13 09:24:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| nl | ns1.dns.nl, ns3.dns.nl, ns4.dns.nl | - |
| royaldating.nl | ns1.dnsmanager.nl, ns2.dnsmanager.nl | 4 records |
✅ Authoritative Response
Server:141.138.151.155
NS records: ns1.dnsmanager.nl, ns2.dnsmanager.nl
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 459ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 3.33.236.10 |
| AAAA | 1 | 2600:9000:a612:55d9:577:681:d7ab:f42b |
| NS | 2 | ns2.dnsmanager.nl, ns1.dnsmanager.nl |
| MX | 1 | . (pri: 0) |
| TXT | 2 | larzpb.rediredge.com, v=spf1 -all |
| SOA | 1 | ns1.dnsmanager.nl hm.mediavillage.nl |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.dnsmanager.nl, ns2.dnsmanager.nl, ns1.dnsmanager.nl...)
Analysis
Hierarchy
royaldating.nl is the parent of mx.royaldating.nl.
IP Addresses
royaldating.nl points to two IPs: 2600:9000:a612:55d9:577:681:d7ab:f42b and 3.33.236.10.
Other host names including camin.eu, juves.nl, 240.eu, konink.nl and abbr.eu share IP numbers with royaldating.nl.
Name Servers
royaldating.nl's delegation uses two name servers, ns1.dnsmanager.nl and ns2.dnsmanager.nl.
royaldating.nl shares the same name server setup as other domains, for example krijtverven.nl, eh2.nl, preventiezorg.nl, organisatierecht.nl and proassist.nl.
Host names with two IPs:
ns1.dnsmanager.nl points to: 2a01:a680:a1:f::155 and 141.138.151.155
ns2.dnsmanager.nl points to: 2a01:a680:a1:f::156 and 141.138.151.156