Skip to content

Hostname

marwa.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:9
Registrant organisation
domain trading
Contact emails
a739m6kz75p@myprivatename.com, bh2ww96w5mv@myprivatename.com, gaberelnaggar@gmail.com, j39ha4dr8s4@myprivatename.com, k89pv7mb2qa@myprivatename.com, kh7mp2mj8x3@myprivatename.com, karim.tazi@marwa.ma

Subdomains

Subdomain
club.marwa.com
myadm.marwa.com
ocr-app.marwa.com
staging.marwa.com
takt.marwa.com
transferts-mags.marwa.com
www.marwa.com
y2-prod.marwa.com
y2-test.marwa.com

Showing 9 of 9 subdomains (9 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

Mail and authentication

Nameservers

  • adel.ns.cloudflare.com
  • ken.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 marwa.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: "marwa.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.