Skip to content

Hostname

boyfriendsingle.com

Last fetched

boyfriendsingle.com resolves to 104.21.26.36, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. boyfriendsingle.com 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 · boyfriendsingle.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/boyfriendsingle.com

Resolution chain

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1418
Registrant organisation
protectservice,
Contact emails
boyfriendsingle.com@whoisprotectservice.net

Subdomains

Subdomain
cc.boyfriendsingle.com
cdn.boyfriendsingle.com
cdn77.boyfriendsingle.com
wildcard.boyfriendsingle.com
www.boyfriendsingle.com

Showing 5 of 5 subdomains (5 per page).

Mail and authentication

Nameservers

  • alan.ns.cloudflare.com
  • irma.ns.cloudflare.com
  • ns.anycastns1.org
  • ns.anycastns2.org

MX records

  • mail.vipmailservice.com

Threat-feed evidence

History

Related pages

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