corefuse.net - robtex.com
corefuse.net
net
| 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=1777018721 | ||||||
Same first word
corefuse.net |
Similar names
DNS History
9 records (7 active, 2 former)
●NSteagan.ns.cloudflare.com2026-02-22 → 2026-04-24 · 2 obs
● 2026-04-24 08:45:06
●NSviddy.ns.cloudflare.com2026-02-22 → 2026-04-24 · 2 obs
● 2026-04-24 08:45:06
●MXcorefuse-net.mail.protection.outlook.com2026-02-22 → 2026-04-24 · 2 obs
● 2026-04-24 08:45:06
●A104.21.33.1672026-02-22 → 2026-04-24 · 4 obs
○ 2026-03-01 02:59:16
● 2026-03-13 14:56:20
● 2026-04-24 08:45:06
○A172.64.80.12026-03-01 → 2026-03-01 · 4 obs
● 2026-03-01 02:59:16
○ 2026-03-13 14:56:20
○ 2026-04-24 08:45:06
●A172.67.165.82026-02-22 → 2026-04-24 · 4 obs
○ 2026-03-01 02:59:16
● 2026-03-13 14:56:20
● 2026-04-24 08:45:06
○A2606:4700:130:436c:6f75:6466:6c61:72652026-03-01 → 2026-03-13 · 5 obs
● 2026-03-01 02:59:16
● 2026-03-13 14:56:20
○ 2026-04-05 09:56:42
○ 2026-04-24 08:45:06
●A2606:4700:3032::6815:21a72026-02-22 → 2026-04-24 · 5 obs
○ 2026-03-01 02:59:16
○ 2026-03-13 14:56:20
● 2026-04-05 09:56:42
● 2026-04-24 08:45:06
●A2606:4700:3035::ac43:a5082026-02-22 → 2026-04-24 · 5 obs
○ 2026-03-01 02:59:16
○ 2026-03-13 14:56:20
● 2026-04-05 09:56:42
● 2026-04-24 08:45:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| corefuse.net | teagan.ns.cloudflare.com, viddy.ns.cloudflare.com | - |
✅ Authoritative Response
Server:162.159.38.174
NS records: teagan.ns.cloudflare.com, viddy.ns.cloudflare.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 552ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.33.167, 172.67.165.8 |
| AAAA | 2 | 2606:4700:3035::ac43:a508, 2606:4700:3032::6815:21a7 |
| NS | 2 | teagan.ns.cloudflare.com, viddy.ns.cloudflare.com |
| MX | 1 | corefuse-net.mail.protection.outlook.com |
| TXT | 7 | MS=ms98770120, apple-domain-verification=qcWpoFioT8DCG4... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | teagan.ns.cloudflare.com dns.cloudflare. |
Analysis
IP Addresses
Four IP numbers are pointed to by corefuse.net: 2606:4700:3032::6815:21a7, 2606:4700:3035::ac43:a508, 104.21.33.167 and 172.67.165.8.
other host names including 76kgg.com, stillpointyoga.net, costaskincare.com, folkehogskolene.net and vosin.cn share IP numbers with corefuse.net.
Name Servers
corefuse.net is delegated to two name servers teagan.ns.cloudflare.com and viddy.ns.cloudflare.com.
corefuse.net shares the same name server setup as other domains, for instance playquzibox.top, to9vamil.digital, hoth5healthinfoy.top, 3zorelin.digital and fux.yachts.
corefuse.net at least partially shares name servers with other domains, for instance shoutout.io, unifiedsignal.com, rdadvertising.org, optants.fr and whsfbsw.com.
These name servers are commonly used with jule.ns.cloudflare.com, amos.ns.cloudflare.com and carl.ns.cloudflare.com.
Host names with six IP numbers:
Host name teagan.ns.cloudflare.com points to: 2606:4700:50::a29f:26ae, 2803:f800:50::6ca2:c2ae, 2a06:98c1:50::ac40:22ae, 108.162.194.174, 162.159.38.174 and 172.64.34.174.
Host name viddy.ns.cloudflare.com points to: 2606:4700:58::a29f:2c63, 2803:f800:50::6ca2:c363, 2a06:98c1:50::ac40:2363, 108.162.195.99, 162.159.44.99 and 172.64.35.99.
Mail Servers
corefuse.net is handled by a single mail server, corefuse-net.mail.protection.outlook.com.
Host corefuse-net.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:cc31::, 2a01:111:f403:cc31::2, 2a01:111:f403:cc31::3, 2a01:111:f403:cc33::, 52.101.149.0, 52.101.149.1, 52.101.149.2 and 52.101.149.9.