refiloop.com - dns.ninja
refiloop.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=1786401349 | ||||||
Same first word
refiloop.com |
Similar names
DNS History
12 records (11 active, 1 former)
●NScuritiba.ns.porkbun.com2026-04-13 → 2026-08-10 · 2 obs
● 2026-08-10 22:52:32
●NSfortaleza.ns.porkbun.com2026-04-13 → 2026-08-10 · 2 obs
● 2026-08-10 22:52:32
●NSmaceio.ns.porkbun.com2026-04-13 → 2026-08-10 · 2 obs
● 2026-08-10 22:52:32
●NSsalvador.ns.porkbun.com2026-04-13 → 2026-08-10 · 2 obs
● 2026-08-10 22:52:32
●MXalt1.aspmx.l.google.com2026-04-13 → 2026-08-10 · 2 obs
● 2026-08-10 22:52:32
●MXalt2.aspmx.l.google.com2026-04-13 → 2026-08-10 · 2 obs
● 2026-08-10 22:52:32
●MXalt3.aspmx.l.google.com2026-04-13 → 2026-08-10 · 2 obs
● 2026-08-10 22:52:32
●MXalt4.aspmx.l.google.com2026-04-13 → 2026-08-10 · 2 obs
● 2026-08-10 22:52:32
●MXaspmx.l.google.com2026-04-13 → 2026-08-10 · 2 obs
● 2026-08-10 22:52:32
●A192.0.79.1292026-05-08 → 2026-08-10 · 3 obs
● 2026-05-08 10:58:44
● 2026-08-10 22:52:32
●A192.0.79.1812026-05-08 → 2026-08-10 · 3 obs
● 2026-05-08 10:58:44
● 2026-08-10 22:52:32
○A34.215.132.292026-04-13 → 2026-04-13 · 3 obs
○ 2026-05-08 10:58:44
○ 2026-08-10 22:52:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| refiloop.com | maceio.ns.porkbun.com, salvador.ns.porkbun.com, fortaleza.ns.porkbun.com, curitiba.ns.porkbun.com | 8 records |
✅ Authoritative Response
Server:162.159.8.140
NS records: maceio.ns.porkbun.com, salvador.ns.porkbun.com, fortaleza.ns.porkbun.com, curitiba.ns.porkbun.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for refiloop.com (unsigned zone)
⏱️ Timing
Total: 1252ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 192.0.79.129, 192.0.79.181 |
| NS | 4 | curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=IFZGmwwguwuPpVg, google-site-verification=dAGQsGfHuMT_keR |
| SOA | 1 | curitiba.ns.porkbun.com dns.cloudflare.c |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (maceio.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com...)
Analysis
IP Addresses
refiloop.com has two IP addresses: 192.0.79.129 and 192.0.79.181
shoresh.com, griffinderm.net, dehartplumbing.com plus two other host names have IP numbers in common with refiloop.com.
Name Servers
Four name servers handle the delegation for refiloop.com: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com and salvador.ns.porkbun.com.
The name servers of refiloop.com overlap at least partially with those of other domains — among them flaptv.com, estradalingsas.com, instagramcreatorcopilot.com and two more.
Each of the four hosts curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com and salvador.ns.porkbun.com has two IP addresses. curitiba.ns.porkbun.com points to 173.245.58.37 and 2400:cb00:2049:1::adf5:3a25. fortaleza.ns.porkbun.com points to 162.159.8.140 and 2400:cb00:2049:1::a29f:88c. maceio.ns.porkbun.com points to 162.159.11.180 and 2400:cb00:2049:1::a29f:bb4. salvador.ns.porkbun.com points to 162.159.10.150 and 2400:cb00:2049:1::a29f:a96.
Mail Servers
Five mail servers handle refiloop.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by refiloop.com are shared with other domains: ns500683.ns500693.ns500468.ns500110.dtrkdll.com, ns500693.ns500734.ns500734.ns500699.ns500693.ns500699.ns500699.ns500588.ns500683.ns500699.ns500699.ns500699.ns500693.ns500699.ns500602.dtrkdll.com, ns500759.ns500759.ns500759.ns500735.ns500736.ns500698.ns500735.ns500698.ns500708.ns500576.ns500686.ns500686.ns500619.ns500619.trackreceptor.com and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com resolves to 142.251.167.26 and 2607:f8b0:4004:c1f::1b.
alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.