rapify.com - dns.ninja
rapify.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 107.152.102.217🇺🇸 COLOAT107.152.102.0/24 COLO@ | ||||||
| NS | ns1.rapifyserver.com ⭐ | ||||||
| A | 107.152.102.215🇺🇸 COLOAT107.152.102.0/24 COLO@ | ||||||
| PTR | server.amirousa.com | ||||||
| NS | ns2.rapifyserver.com | ||||||
| A | 107.152.102.216🇺🇸 COLOAT107.152.102.0/24 COLO@ | ||||||
| MX | rapify.com ⭐ | ||||||
| A | 107.152.102.217🇺🇸 COLOAT107.152.102.0/24 COLO@ | ||||||
| TXT | v=spf1 ip4:107.152.102.215 +a +mx ~all | ||||||
| SOA | ns1.rapifyserver.comsupport@wpgateway.com 2026-03-12 #17 | ||||||
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=1782463465 | ||||||
MX for
rapify.com |
Same first word
Similar names
ifrpay.com |
pairfy.com |
rfipay.com |
firpay.com |
fripay.com |
parify.co.uk |
pafiry.net |
iyfrap.com |
aprify.com |
parify.org |
firapy.com |
parify.me |
rifpay.com |
payfri.com |
ipfray.com |
DNS History
13 records (4 active, 9 former)
○NSdns1.hopmanportal.com2017-05-17 → 2017-05-17 · 4 obs
○ 2017-01-30 02:02:44
● 2017-05-17 04:55:16
○ 2026-04-15 15:18:40
○ 2026-06-26 08:54:30
● 2017-05-17 04:55:16
○ 2026-04-15 15:18:40
○ 2026-06-26 08:54:30
○NSdns1.icertified.net2017-01-30 → 2017-01-30 · 4 obs
○ 2016-05-07 09:03:28
● 2017-01-30 02:02:44
○ 2017-05-17 04:55:16
○ 2026-06-26 08:54:30
● 2017-01-30 02:02:44
○ 2017-05-17 04:55:16
○ 2026-06-26 08:54:30
○NSdns2.hopmanportal.com2017-05-17 → 2017-05-17 · 4 obs
○ 2017-01-30 02:02:44
● 2017-05-17 04:55:16
○ 2026-04-15 15:18:40
○ 2026-06-26 08:54:30
● 2017-05-17 04:55:16
○ 2026-04-15 15:18:40
○ 2026-06-26 08:54:30
○NSdns2.icertified.net2017-01-30 → 2017-01-30 · 4 obs
○ 2016-05-07 09:03:28
● 2017-01-30 02:02:44
○ 2017-05-17 04:55:16
○ 2026-06-26 08:54:30
● 2017-01-30 02:02:44
○ 2017-05-17 04:55:16
○ 2026-06-26 08:54:30
○NSns1.bodis.com2015-07-09 → 2016-05-07 · 4 obs
● 2015-07-09 23:01:52
● 2016-05-07 09:03:28
○ 2017-01-30 02:02:44
○ 2026-06-26 08:54:30
● 2016-05-07 09:03:28
○ 2017-01-30 02:02:44
○ 2026-06-26 08:54:30
●NSns1.rapifyserver.com2026-04-15 → 2026-06-26 · 3 obs
○ 2017-05-17 04:55:16
● 2026-04-15 15:18:40
● 2026-06-26 08:54:30
● 2026-04-15 15:18:40
● 2026-06-26 08:54:30
○NSns2.bodis.com2015-07-09 → 2016-05-07 · 4 obs
● 2015-07-09 23:01:52
● 2016-05-07 09:03:28
○ 2017-01-30 02:02:44
○ 2026-06-26 08:54:30
● 2016-05-07 09:03:28
○ 2017-01-30 02:02:44
○ 2026-06-26 08:54:30
●NSns2.rapifyserver.com2026-04-15 → 2026-06-26 · 3 obs
○ 2017-05-17 04:55:16
● 2026-04-15 15:18:40
● 2026-06-26 08:54:30
● 2026-04-15 15:18:40
● 2026-06-26 08:54:30
●MXrapify.com2017-01-30 → 2026-06-26 · 2 obs
● 2017-01-30 02:02:44
● 2026-06-26 08:54:30
● 2026-06-26 08:54:30
●A107.152.102.2172026-04-15 → 2026-06-26 · 3 obs
○ 2017-05-17 04:55:16
● 2026-04-15 15:18:40
● 2026-06-26 08:54:30
● 2026-04-15 15:18:40
● 2026-06-26 08:54:30
○A173.45.160.812017-05-17 → 2017-05-17 · 4 obs
○ 2017-01-30 02:02:44
● 2017-05-17 04:55:16
○ 2026-04-15 15:18:40
○ 2026-06-26 08:54:30
● 2017-05-17 04:55:16
○ 2026-04-15 15:18:40
○ 2026-06-26 08:54:30
○A173.45.173.1802017-01-30 → 2017-01-30 · 4 obs
○ 2016-05-07 09:03:28
● 2017-01-30 02:02:44
○ 2017-05-17 04:55:16
○ 2026-06-26 08:54:30
● 2017-01-30 02:02:44
○ 2017-05-17 04:55:16
○ 2026-06-26 08:54:30
○A199.59.243.1202015-07-09 → 2016-05-07 · 4 obs
● 2015-07-09 23:01:52
● 2016-05-07 09:03:28
○ 2017-01-30 02:02:44
○ 2026-06-26 08:54:30
● 2016-05-07 09:03:28
○ 2017-01-30 02:02:44
○ 2026-06-26 08:54:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, e.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net... | - |
| rapify.com | ns1.rapifyserver.com, ns2.rapifyserver.com | 2 records |
✅ Authoritative Response
Server:107.152.102.216
NS records: ns1.rapifyserver.com, ns2.rapifyserver.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rapify.com (unsigned zone)
⏱️ Timing
Total: 435ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 107.152.102.217 |
| NS | 2 | ns2.rapifyserver.com, ns1.rapifyserver.com |
| MX | 1 | rapify.com (pri: 0) |
| TXT | 1 | v=spf1 ip4:107.152.102.215 +a +mx ~all |
| SOA | 1 | ns1.rapifyserver.com support.wpgateway.c |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.rapifyserver.com, ns2.rapifyserver.com)
Analysis
Mail Server Role
rapify.com serves as a mail server for rapify.com.
IP Addresses
rapify.com has exactly one IP address — 107.152.102.217.
Name Servers
Two name servers handle the delegation for rapify.com: ns1.rapifyserver.com and ns2.rapifyserver.com.
ns1.rapifyserver.com and ns2.rapifyserver.com each resolve to one IP number: ns1.rapifyserver.com points to 107.152.102.215 and ns2.rapifyserver.com points to 107.152.102.216.
Mail Servers
rapify.com uses exactly one mail server, which is rapify.com.
rapify.com carries a single IP number, which is 107.152.102.217.