Skip to content

Hostname

kinobd.net

Last fetched

kinobd.net resolves to 104.21.88.74, announced in 104.21.80.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. kinobd.net is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · kinobd.netRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/kinobd.net

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2487
Registrant organisation
domain admin
Contact emails
cd695e55be8a4cc1b1d00b26e31c29e7.protect@whoisguard.com, owner@kinobd.net.customers.whoisprivacycorp.com, kinobd.net-owner-euag@customers.whoisprivacycorp.com, kinobd.net-owner-je54@customers.whoisprivacycorp.com

Subdomains

Subdomain
autoconfig.kinobd.net
nserv.kinobd.net
sentry.kinobd.net
status.kinobd.net
www.kinobd.net
zab.kinobd.net

Showing 6 of 6 subdomains (6 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • maria.ns.cloudflare.com
  • mario.ns.cloudflare.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • aspmx1.migadu.com
  • aspmx2.migadu.com
  • route1.mx.cloudflare.net
  • route2.mx.cloudflare.net
  • route3.mx.cloudflare.net

SPF policy

  • include: spf.migadu.com

Threat-feed evidence

History

Related pages

Pivot from kinobd.net into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "kinobd.net"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.