Example — mago.team public sources
INTELLIGENCE REPORT

mago.team

DOMAIN OSINT ANALYSIS
Sun, 20 Sep 2026 00:00:00 GMT · EXAMPLE
Recon score
3 INFO

Executive Summary

01

Strong passive signal profile

mago.team is a Cloudflare-fronted domain. Public DNS shows Cloudflare nameservers, anycast A/AAAA, and Cloudflare MX. Certificate Transparency lists TLS coverage for the apex. This example uses only public DNS and CT — no people-search, no third-party mailboxes, no synthetic host.

  • Treat this page as a sample of a domain search on mago.team public sources
  • Paid search (Detective $49) adds more modules on a target you authorize

Target Intelligence

02
Valuemago.team
Typedomain

Findings (3)

03
OSINT signals
IDSeverityFinding
m-001INFO
Apex served through Cloudflare anycast
Public A and AAAA records for mago.team sit on Cloudflare anycast ranges. That is a CDN/proxy signal, not a vulnerability.
Public A/AAAA on Cloudflare anycast. Exact octets in the DNS section of this example.
m-002INFO
Nameservers and mail on Cloudflare
NS and MX are Cloudflare. SPF authorizes Cloudflare outbound mail. No third-party mailbox is listed here.
NS milan.ns.cloudflare.com, teresa.ns.cloudflare.com. MX route1/2/3.mx.cloudflare.net. TXT v=spf1 include:_spf.mx.cloudflare.net ~all.
m-003INFO
Certificate Transparency covers mago.team
CT logs publish certificates for the apex used by the public site. This example does not invent a subdomain count.
Target mago.team. Public CT name: mago.team. blog.mago.team is a published hostname on the same zone.

DNS / WHOIS

04
DNS topology
mago.teammago.teamA 104.21.36.92A 104.21.36.92A 172.67.191.195A 172.67.191.195NS milan.ns.cloudflare.comNS milan.ns.cloudflare.comNS teresa.ns.cloudflare.comNS teresa.ns.cloudflare.comMX route1.mx.cloudflare.netMX route1.mx.cloudflare.netMX route2.mx.cloudflare.netMX route2.mx.cloudflare.netMX route3.mx.cloudflare.netMX route3.mx.cloudflare.nethost blog.mago.teamhost blog.mago.team
PlatformPageNamePublic text
A 104.21.36.92A 104.21.36.92—Existence only. Title and bio were not extracted in this scan.
A 172.67.191.195A 172.67.191.195—Existence only. Title and bio were not extracted in this scan.
NS milan.ns.cloudflare.comNS milan.ns.cloudflare.com—Existence only. Title and bio were not extracted in this scan.
NS teresa.ns.cloudflare.comNS teresa.ns.cloudflare.com—Existence only. Title and bio were not extracted in this scan.
MX route1.mx.cloudflare.netMX route1.mx.cloudflare.net—Existence only. Title and bio were not extracted in this scan.
MX route2.mx.cloudflare.netMX route2.mx.cloudflare.net—Existence only. Title and bio were not extracted in this scan.
MX route3.mx.cloudflare.netMX route3.mx.cloudflare.net—Existence only. Title and bio were not extracted in this scan.
host blog.mago.teamhost blog.mago.team—Existence only. Title and bio were not extracted in this scan.
A
104.21.36.92
172.67.191.195
MX
route1.mx.cloudflare.net
route2.mx.cloudflare.net
route3.mx.cloudflare.net
NS
milan.ns.cloudflare.com
teresa.ns.cloudflare.com
TXT
v=spf1 include:_spf.mx.cloudflare.net ~all
SUBDOMAINS
blog.mago.team

Methodology

05
OfferInfrastructure recon
ScopePassive public DNS and CT for mago.team only.
AuthorizationSelf-target example. No third-party PII.
Modules2 executed
dns enumcert transparency
NEW SCANVIEW HISTORY