Skip to content

Hostname

yoopiesatwork.com

Last fetched

yoopiesatwork.com resolves to 104.21.44.142, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. yoopiesatwork.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 · yoopiesatwork.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/yoopiesatwork.com

Resolution chain

IPv6 resolution

No AAAA record for yoopiesatwork.com is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
yoopies s.a.s.
Contact emails
06737aada1f64644b081d9d712a7fce1-2428388@contact.gandi.net, 134484636b42c49267afbc8d6b625952-2428388@contact.gandi.net, 5824f1da-37f6-4926-acd3-898eae4b80c0@identity-protect.org, 93727a6a-5d55-4ed8-9a52-ebf1e491f9f0@identity-protect.org

Subdomains

Subdomain
blog.yoopiesatwork.com
upload.yoopiesatwork.com

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • collins.ns.cloudflare.com
  • renan.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

Pivot from yoopiesatwork.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: "yoopiesatwork.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.