Skip to content

Hostname

boyscom.de

Last fetched

boyscom.de resolves to 104.21.49.14, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. boyscom.de 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 · boyscom.deRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/boyscom.de

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for boyscom.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
1.boyscom.de
2923f0a7615e.boyscom.de
a5z4aqs34t24qts.boyscom.de
api.boyscom.de
autodiscover.boyscom.de
backend.boyscom.de
bc2020.boyscom.de
blackpanda.boyscom.de
chat.boyscom.de
cloud.boyscom.de
cmsserver.boyscom.de
cpanel.boyscom.de

Showing 12 of 115. View all subdomains →

Mail and authentication

Nameservers

  • aaron.ns.cloudflare.com
  • joyce.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
  • ns3.stratoserver.net
  • ns4.stratoserver.net

MX records

  • boyscom.de
  • _dc-mx.2923f0a7615e.boyscom.de

SPF policy

  • include: _spf.google.com
  • a: boyscom.de
  • mx: boyscom.de
  • a: mail.boyscom.de
  • mx: mail.boyscom.de
  • ip: 81.169.235.3

Threat-feed evidence

History

Related pages

Pivot from boyscom.de 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: "boyscom.de"})-[: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.