wouldmeet.com - robtex.com
wouldmeet.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 64.38.230.2🇺🇸 AS2045464.38.224.0/20 Proxy route | ||||||
| NS | ns1.r4l.com ⭐ | ||||||
| A | 2607:5300:60:34bf::1🇨🇦 OVH2607:5300::/32 Hosting route | ||||||
| A | 142.4.204.181🇨🇦 OVH142.4.192.0/19 Hosting route | ||||||
| PTR | mxgw.r4l.com | ||||||
| NS | ns2.r4l.com | ||||||
| A | 2600:3c03::f03c:91ff:fe93:e369🇺🇸 AKAMAI-LINODE-AP2600:3c03::/32 Akamai Technologies | ||||||
| PTR | ns2.r4l.com | ||||||
| A | 66.228.40.6🇺🇸 AKAMAI-LINODE-AP66.228.32.0/20 Akamai Technologies | ||||||
| PTR | ns2.r4l.com | ||||||
| MX | mx1.r4l.com ⭐ | ||||||
| A | 192.99.3.191🇨🇦 OVH192.99.0.0/16 Hosting route | ||||||
| PTR | smtp.r4l.com | ||||||
| MX | mx2.r4l.com ⭐ | ||||||
| A | 192.99.3.191🇨🇦 OVH192.99.0.0/16 Hosting route | ||||||
| PTR | smtp.r4l.com | ||||||
| MX | mx3.r4l.com ⭐ | ||||||
| A | 192.99.3.191🇨🇦 OVH192.99.0.0/16 Hosting route | ||||||
| PTR | smtp.r4l.com | ||||||
| TXT | v=spf1 redirect=r4l.com | ||||||
| SOA | ns1.r4l.comsupport@register4less.com serial=1542968438 | ||||||
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
wouldmeet.com |
DNS History
6 records (6 active, 0 former)
●A64.38.230.22015-08-02 → 2026-03-12 · 2 obs
● 2026-03-12 21:10:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| wouldmeet.com | ns1.r4l.com, ns2.r4l.com | 4 records |
✅ Authoritative Response
Server: 66.228.40.6
NS records: ns1.r4l.com, ns2.r4l.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for wouldmeet.com (unsigned zone)
⏱️ Timing
Total: 239ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 64.38.230.2 |
| NS | 2 | ns2.r4l.com, ns1.r4l.com |
| MX | 3 | mx3.r4l.com (pri: 10), mx1.r4l.com (pri: 10)... |
| TXT | 1 | v=spf1 redirect=r4l.com |
| SOA | 1 | ns1.r4l.com support.register4less.com |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.r4l.com, ns1.r4l.com, ns2.r4l.com...)
Analysis
IP Addresses
wouldmeet.com points to a single IP: 64.38.230.2.
Other host names, for instance corruptangels.com, live(0x736578)bate.com, couplestream.com, latinvirgins.com and asianvirgins.com share IP numbers with wouldmeet.com.
Name Servers
wouldmeet.com's delegation is to two name servers ns1.r4l.com and ns2.r4l.com.
wouldmeet.com shares the same name server configuration as other domains, such as eibox.com, pipetapes.com, pointcore.org, ghosthour.com and stepmomsorority.com.
wouldmeet.com shares name servers with other domains to at least some extent, for instance bilderbergers.org and bluehades.com.
Host names with two IP numbers: ns1.r4l.com points to 2607:5300:60:34bf::1 and 142.4.204.181; ns2.r4l.com points to 2600:3c03::f03c:91ff:fe93:e369 and 66.228.40.6
Mail Servers
wouldmeet.com is handled by three mail servers: mx1.r4l.com, mx2.r4l.com and mx3.r4l.com.
wouldmeet.com shares some mail servers with other domains, including batsakes.com, nationalfathersresourcecenter.com, mycoa.ch, familywithextracheese.com and shopgrandcitiesmall.com.
Host names with one IP
mx1.r4l.com points to: 192.99.3.191.
mx2.r4l.com points to: 192.99.3.191.
mx3.r4l.com points to: 192.99.3.191.
Host names pointing to 192.99.3.191: mx1.r4l.com, mx2.r4l.com and mx3.r4l.com.