Skip to content

Hostname

scoober.com

Last fetched

scoober.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. scoober.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 · scoober.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/scoober.com

Resolution chain

No IPv4 resolution is recorded for scoober.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:2288
Registrant organisation
on behalf of scoober.com owner
Contact emails
it.te@takeaway.com, team-pcit+domains@takeaway.com, owner-10231838@scoober.com.whoisprivacyservice.org, owner-10304405@scoober.com.whoisprivacyservice.org, owner-10594673@scoober.com.whoisprivacyservice.org, owner-10957110@scoober.com.whoisprivacyservice.org, owner-2662369@scoober.com.whoisprivacyservice.org, owner-290152@scoober.com.whoisprivacyservice.org, owner-3794977@scoober.com.whoisprivacyservice.org, owner-4064926@scoober.com.whoisprivacyservice.org, owner-4447682@scoober.com.whoisprivacyservice.org, owner-6364576@scoober.com.whoisprivacyservice.org, owner-757483@scoober.com.whoisprivacyservice.org, owner@scoober.com.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-470.awsdns-58.com
  • ns-585.awsdns-09.net
  • ns-1444.awsdns-52.org
  • ns-1946.awsdns-51.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • mx: scoober.com
  • include: spf.sendinblue.com
  • include: servers.mcsv.net

Threat-feed evidence

History

Related pages

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