mailurity.dev - robtex.com
mailurity.dev
| DNSSEC | ⚠️ Not signed | ||||||
| A | 136.243.188.6🇩🇪 Hetzner136.243.0.0/16 HETZNER-RZ-BLK-ERX3 | ||||||
| PTR | cp1.fmopz.systems | ||||||
| NS | ns1.fmopz.net ⭐ | ||||||
| A | 2a01:4f8:200:247a::4🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK | ||||||
| PTR | ns1.fmopz.systems | ||||||
| A | 136.243.188.10🇩🇪 Hetzner136.243.0.0/16 HETZNER-RZ-BLK-ERX3 | ||||||
| PTR | ns1.fmopz.net | ||||||
| NS | ns2.fmopz.net | ||||||
| A | 2a01:4f9:c015:9cd4::1🇩🇪 Hetzner2a01:4f9::/32 HETZNER-IPv6-BLK | ||||||
| PTR | ns2.fmopz.net | ||||||
| A | 135.181.89.101🇫🇮 Hetzner135.181.0.0/16 HETZNER-DC | ||||||
| PTR | ns2.fmopz.net | ||||||
| MX | mailurity.dev ⭐ | ||||||
| A | 136.243.188.6🇩🇪 Hetzner136.243.0.0/16 HETZNER-RZ-BLK-ERX3 | ||||||
| PTR | cp1.fmopz.systems | ||||||
| TXT | v=spf1 ip4:136.243.188.6 +a +mx ~all | ||||||
| SOA | ns1.fmopz.netreports@fmopz.systems 2026-08-31 #4 | ||||||
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
MX for
mailurity.dev |
Same first word
mailurity.eu |
mailurity.com |
mailurity.xyz |
mailurity.net |
mailurity.cloud |
mailurity.pt |
mailurity.dev |
mailurity.org |
Similar names
Previous names
Next names
DNS History
4 records (4 active, 0 former)
●MXmailurity.dev2026-08-29 → 2026-09-04 · 2 obs
● 2026-09-04 18:03:08
●A136.243.188.62026-08-29 → 2026-09-04 · 2 obs
● 2026-09-04 18:03:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | - |
| mailurity.dev | ns2.fmopz.net, ns1.fmopz.net | - |
✅ Authoritative Response
Server:135.181.89.101
NS records: ns2.fmopz.net, ns1.fmopz.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mailurity.dev (unsigned zone)
⏱️ Timing
Total: 1029ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 136.243.188.6 |
| NS | 2 | ns1.fmopz.net, ns2.fmopz.net |
| MX | 1 | mailurity.dev (pri: 0) |
| TXT | 1 | v=spf1 ip4:136.243.188.6 +a +mx ~all |
| SOA | 1 | ns1.fmopz.net reports.fmopz.systems |
Analysis
Mail Server Role
mailurity.dev serves as a mail server for mailurity.dev.
IP Addresses
mailurity.dev has exactly one IP address — 136.243.188.6.
cpstat.org, mailurity.cloud, fmopz.com plus two other host names have IP numbers in common with mailurity.dev.
Name Servers
The NS records for mailurity.dev delegate to ns1.fmopz.net and ns2.fmopz.net.
The name server configuration of mailurity.dev is shared with other domains, for instance fmop.app, cpstat.cloud, cpstat.app and two others.
ns1.fmopz.net resolves to 136.243.188.10 and 2a01:4f8:200:247a::4. Likewise, ns2.fmopz.net resolves to 135.181.89.101 and 2a01:4f9:c015:9cd4::1 — two IP addresses apiece.
Mail Servers
mailurity.dev uses exactly one mail server, which is mailurity.dev.
mailurity.dev resolves to 136.243.188.6 and no other IP number.